-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An error log occurs repeatedly in the deployment logs of amazon-cloudwatch-observability-controller-manager. #269
Comments
Hey @wontae913 , are you overriding the default add-on configuration ? It seems like the operator did not create a service for the AmazonCloudWatchAgent and hence failed to create the liveness probe as well |
hello @mitali-salvi |
@mitali-salvi I'm also facing the same issue. EKS version is here is my add-on configuration:
|
Hi @movence @mitali-salvi Is there anything we can do to assist with this? |
I'm facing the same problem as well. Is this expected? It spams the logs constantly. |
I am facing same problem eks 1.31 aws-observability addon verison 3.1.0 |
eks version : 1.30
add-on for eks: amazon-cloudwatch-observability
version: v2.2.0-eksbuild.1
deployment.apps/amazon-cloudwatch-observability-controller-manager
image: cloudwatch-agent-operator:1.8.0
kubectl -namazon-cloudwatch logs deployment.apps/amazon-cloudwatch-observability-controller-manager
{"level":"error","ts":"2024-11-06T01:27:19Z","logger":"controllers.AmazonCloudWatchAgent","msg":"cannot create liveness probe.","error":"no service available as part of the configuration","stacktrace":"github.com/aws/amazon-cloudwatch-agent-operator/internal/manifests/collector.Container\n\t/workspace/internal/manifests/collector/container.go:92\ngithub.com/aws/amazon-cloudwatch-agent-operator/internal/manifests/collector.DaemonSet\n\t/workspace/internal/manifests/collector/daemonset.go:42\ngithub.com/aws/amazon-cloudwatch-agent-operator/internal/manifests/collector.Build.func5\n\t/workspace/internal/manifests/builder.go:20\ngithub.com/aws/amazon-cloudwatch-agent-operator/internal/manifests/collector.Build\n\t/workspace/internal/manifests/collector/collector.go:51\ngithub.com/aws/amazon-cloudwatch-agent-operator/controllers.BuildCollector\n\t/workspace/controllers/common.go:50\ngithub.com/aws/amazon-cloudwatch-agent-operator/controllers.(*AmazonCloudWatchAgentReconciler).Reconcile\n\t/workspace/controllers/amazoncloudwatchagent_controller.go:107\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:316\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:227"}
Is it possible to take action by changing the settings? There appears to be no livenessprobe related information in yaml.
The text was updated successfully, but these errors were encountered: