You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/containers/kubernetes/control_plane.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ By providing read access to the Etcd certificates located on the host, the Datad
55
55
56
56
Custom `values.yaml`:
57
57
58
-
```
58
+
```yaml
59
59
datadog:
60
60
apiKey: <DATADOG_API_KEY>
61
61
appKey: <DATADOG_APP_KEY>
@@ -93,7 +93,7 @@ agents:
93
93
94
94
DatadogAgent Kubernetes Resource:
95
95
96
-
```
96
+
```yaml
97
97
apiVersion: datadoghq.com/v1alpha1
98
98
kind: DatadogAgent
99
99
metadata:
@@ -165,7 +165,7 @@ Secure ports allow authentication and authorization to protect your Control Plan
165
165
166
166
Custom `values.yaml`:
167
167
168
-
```
168
+
```yaml
169
169
datadog:
170
170
apiKey: <DATADOG_API_KEY>
171
171
appKey: <DATADOG_APP_KEY>
@@ -219,7 +219,7 @@ agents:
219
219
220
220
DatadogAgent Kubernetes Resource:
221
221
222
-
```
222
+
```yaml
223
223
apiVersion: datadoghq.com/v1alpha1
224
224
kind: DatadogAgent
225
225
metadata:
@@ -303,7 +303,7 @@ data:
303
303
- The `ssl_verify` field in the `kube_controller_manager` and `kube_scheduler` configuration needs to be set to `false` when using self-signed certificates.
304
304
- When targeting secure ports, the `bind-address` option in your Controller Manager and Scheduler configuration must be reachable by the Datadog Agent. Example:
305
305
306
-
```
306
+
```yaml
307
307
apiVersion: kubeadm.k8s.io/v1beta2
308
308
kind: ClusterConfiguration
309
309
controllerManager:
@@ -703,7 +703,7 @@ Deploy the Datadog Agent with manifests based on the following configurations:
703
703
704
704
Custom `values.yaml`:
705
705
706
-
```
706
+
```yaml
707
707
datadog:
708
708
apiKey: <DATADOG_API_KEY>
709
709
appKey: <DATADOG_APP_KEY>
@@ -733,7 +733,7 @@ agents:
733
733
734
734
DatadogAgent Kubernetes Resource:
735
735
736
-
```
736
+
```yaml
737
737
apiVersion: datadoghq.com/v1alpha1
738
738
kind: DatadogAgent
739
739
metadata:
@@ -820,7 +820,7 @@ The following are examples of how to configure the Datadog Agent with Helm and t
0 commit comments