Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
D
docs
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Administrator
docs
Commits
3f3c1d0f
Commit
3f3c1d0f
authored
Oct 26, 2015
by
Jimmi Dyson
Committed by
Fabian Reinartz
Jan 27, 2016
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Kubernetes SD: API server config rename and auth options update
parent
d4748699
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
21 additions
and
14 deletions
+21
-14
configuration.md
content/docs/operating/configuration.md
+21
-14
No files found.
content/docs/operating/configuration.md
View file @
3f3c1d0f
...
...
@@ -307,16 +307,16 @@ likely in future releases.
Kubernetes SD configurations allow retrieving scrape targets from
[
Kubernetes'
](
http://kubernetes.io/
)
REST API. By default, this discovers
mast
ers, nodes, and appropriately annotated services so that metrics from both
API serv
ers, nodes, and appropriately annotated services so that metrics from both
cluster components and deployed applications can be scraped. This will create
multiple target groups: one for all
masters with each mast
er as a target, one
multiple target groups: one for all
API servers with each API serv
er as a target, one
for all nodes with each node as a target, and one for each service containing
each service endpoint as a target.
The following meta labels are available on targets during relabeling:
*
`__meta_kubernetes_role`
: the role of the target: one of
`
master`
,
`node`
or
`service`
*
`__meta_kubernetes_role`
: the role of the target: one of
`
apiserver`
,
`node`
or
`service`
*
`__meta_kubernetes_node_label_<labelname>`
: each node label from the
Kubernetes API
*
`__meta_kubernetes_service_namespace`
: the namespace of the service
...
...
@@ -334,9 +334,9 @@ See below for the configuration options for Kubernetes discovery:
```
# The information to access the Kubernetes API.
# The
mast
er addresses. In a cluster this will normally be
# `https://kubernetes.default.svc`. Supports multiple HA
mast
ers.
mast
ers:
# The
API serv
er addresses. In a cluster this will normally be
# `https://kubernetes.default.svc`. Supports multiple HA
API serv
ers.
api_serv
ers:
- [<host>]
# Run in cluster. This will use the automounted CA certificate and bearer
...
...
@@ -347,14 +347,21 @@ masters:
# port of 10255 (default).
[ kubelet_port: <int> ]
# File to read the bearer token from to authenticate to the API server. If
# running in a pod, then it is best to use a service account and set in_cluster
# to true.
[ bearer_token_file: <filename> ]
# Optional authentication information used to authenticate to the API server.
# Note that `basic_auth`, `bearer_token` and `bearer_token_file` options are
# mutually exclusive.
# Username and password for basic authentication to the API server.
[ username: <string> ]
[ password: <string> ]
# Optional HTTP basic authentication information.
basic_auth:
[ username: <string> ]
[ password: <string> ]
# Optional bearer token authentication information.
[ bearer_token: <string> ]
# Optional bearer token file authentication information. If running in a pod,
# then it is best to use a service account and set in_cluster to true.
[ bearer_token_file: <filename> ]
# TLS configuration. If running in a pod, then it is best to use a service
# account and set in_cluster to true.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment