$ kubectl get po -n amazon-cloudwatch
NAME READY STATUS RESTARTS AGE
cloudwatch-agent-58t6b 0/1 CrashLoopBackOff 10 38m
After
$ kubectl -n amazon-cloudwatch logs --follow cloudwatch-agent-4fcqh
[...]
2019-08-23T13:13:37Z I! k8sapiserver OnStartedLeading: ip-192-168-62-114.ap-northeast-1.compute.internal
2019-08-23T13:13:45Z W! It is the 0 time, going to sleep 200ms before retrying.
$ kubectl get po -n amazon-cloudwatch
NAME READY STATUS RESTARTS AGE
cloudwatch-agent-4fcqh 1/1 Running 0 6m5s
Fixes #12. Follows up on #3.
Why?
How?
eks-gitops-example
's manifests were all updated with the latest manifests from:Only the following ones had changed:
amazon-cloudwatch/cloudwatch-agent-daemonset.yaml
amazon-cloudwatch/cloudwatch-agent-rbac.yaml
Before
After