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
Update APM application linking instructions for Kubernetes
Depends on newrelic/k8s-metadata-injection#701 being merged first, which updates the logging strategy of the k8s-metadata-injection mutating web hook component.
Copy file name to clipboardExpand all lines: src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-apm-applications-kubernetes.mdx
+14-16Lines changed: 14 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -225,22 +225,18 @@ Follow these troubleshooting tips as needed.
225
225
226
226
### Solution
227
227
228
-
1. Verify that the environment variables are set correctly injected by following the instructions described in the [Validate the injection of metadata](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection#validate-injection) section.
228
+
1. Verify that the environment variables have been correctly injected into new pods by following the instructions described in the [Validate the injection of metadata](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection#validate-injection) section.
229
229
230
-
2. If they do not exist, get the name of the metadata injection pod by running:
230
+
2. If they do not exist, firstly, tail the logs of the webhook service:
231
231
232
232
```shell
233
-
kubectl get pods | grep newrelic-metadata-injection-deployment
3. In another terminal, create a new pod and inspect the logs of the metadata injection deployment for errors. See [Validate the injection of metadata](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection#validate-injection) section to create a new pod. For each pod created, there should be a set of 4 new entries in the logs, such as:
236
+
3. In another terminal, create a new pod and inspect the logs of the metadata injection deployment for errors. See [Validate the injection of metadata](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection#validate-injection) section to create a new pod. For each pod created, there should be log entry, assuming the [log level (logLevel)](https://github.com/newrelic/k8s-metadata-injection/blob/main/charts/nri-metadata-injection/README.md#values) is at INFO or lower:
238
237
239
238
```json
240
-
{"level":"info","ts":"2020-04-09T12:55:32.107Z","caller":"server/main.go:139","msg":"POST https://newrelic-metadata-injection-svc.default.svc:443/mutate?timeout=30s HTTP/2.0\" from 10.11.49.2:32836"}
If there are no new entries in the logs, it means that the API server can't communicate with the webhook service, this could be due to network rules or security groups rejecting the communication.
@@ -289,16 +285,18 @@ Follow these troubleshooting tips as needed.
289
285
290
286
6. If there are no log entries in either the API server logs or the metadata injection deployment, it means that the webhook was not registered properly.
291
287
292
-
7. Ensure the metadata injection setup job ran successfully by inspecting the output of this command:
288
+
7. Ensure the metadata injection setup jobs ran successfully by inspecting the output of this command:
293
289
294
290
```shell
295
-
kubectl get job newrelic-metadata-setup
291
+
kubectl get job nri-metadata-injection-admission-create
292
+
kubectl get job nri-metadata-injection-admission-patch
296
293
```
297
294
298
295
8. If the job isn't completed, investigate the logs of the setup job:
0 commit comments