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
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: _includes/gdi/troubleshoot-zeroconfig-k8s.rst
-11Lines changed: 0 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,17 +21,6 @@ Examine logs to make sure that the operator and cert manager are working.
21
21
* ``kubectl logs -l app=cainjector``
22
22
* ``kubectl logs -l app=webhook``
23
23
24
-
Resolve certificate manager issues
25
-
----------------------------------------
26
-
27
-
A hanging operator can indicate issues with the certificate manager.
28
-
29
-
* Check the logs of your cert-manager pods.
30
-
* Restart the cert-manager pods.
31
-
* Ensure that your cluster has only one instance of cert-manager. This includes ``certmanager``, ``certmanager-cainjector``, and ``certmanager-webhook``.
32
-
33
-
See the official cert manager troubleshooting guide for more information: :new-page:`https://cert-manager.io/docs/troubleshooting/`.
Copy file name to clipboardExpand all lines: gdi/opentelemetry/automatic-discovery/k8s/k8s-backend.rst
+7-24Lines changed: 7 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,25 +87,14 @@ Populate values.yaml with the following fields and values:
87
87
operatorcrds:
88
88
install: true
89
89
90
-
You might need to populate the file with additional values depending on your environment. See :ref:`k8s-auto-discovery-add-certificates` and :ref:`k8s-auto-discovery-setup-traces` for more information.
90
+
You might need to populate the file with additional values depending on your environment. See :ref:`k8s-auto-discovery-add-crds` and :ref:`k8s-auto-discovery-setup-traces` for more information.
91
91
92
-
.. _k8s-auto-discovery-add-certificates:
92
+
.. _k8s-auto-discovery-add-crds:
93
93
94
-
Add certificates and OpenTelemetry CRDs
94
+
Add OpenTelemetry CRDs
95
95
------------------------------------------
96
96
97
-
The Operator requires certain TLS certificates to work. Use the following command to check whether a certificate manager is available:
98
-
99
-
.. code-block:: yaml
100
-
101
-
# Check if cert-manager is already installed, don't deploy a second cert-manager.
102
-
kubectl get pods -l app=certmanager --all-namespaces
103
-
104
-
If a certificate manager isn't available in the cluster, add ``certmanager.enabled=true`` to your values.yaml file.
105
-
106
-
The Operator for Kubernetes also requires you to install OpenTelemetry Custom Resource Definitions (CRDs). To do this, add ``operatorcrds.install=true`` to your values.yaml file.
107
-
108
-
The following example YAML includes ``certmanager.enabled=true`` and ``operatorcrds.install=true``:
97
+
The Operator for Kubernetes requires you to install OpenTelemetry Custom Resource Definitions (CRDs). To do this, add ``operatorcrds.install=true`` to your values.yaml file:
109
98
110
99
.. code-block:: yaml
111
100
:emphasize-lines: 7,8
@@ -115,9 +104,7 @@ The following example YAML includes ``certmanager.enabled=true`` and ``operatorc
115
104
splunkObservability:
116
105
realm: <splunk_realm>
117
106
accessToken: <splunk_access_token>
118
-
119
-
certmanager:
120
-
enabled: true
107
+
121
108
operator:
122
109
enabled: true
123
110
operatorcrds:
@@ -248,27 +235,23 @@ Verify all the OpenTelemetry resources are deployed successfully
248
235
249
236
Resources include the Collector, the Operator, webhook, and instrumentation. Run the following commands to verify the resources are deployed correctly.
250
237
251
-
The pods running in the collector namespace must include the following:
238
+
The pods running in the Collector namespace must include the following:
0 commit comments