-
Notifications
You must be signed in to change notification settings - Fork 468
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
POD annotations are dropped with the reconcile of CHK STS #1469
Comments
Signed-off-by: Jiří Kozlovský <jirislav@users.noreply.github.com>
Signed-off-by: Jiří Kozlovský <jirislav@users.noreply.github.com>
Please see this pull request to the branch 0.24.0 🙏🏿 . |
I encountered a similar issue when adding additional annotations for Datadog agent metrics scraping. Here are the details:
|
We are also randomly seeing reconciler errors on some deploys. since we are using annotations in our env, i would suspect it's the same issue as above mentioned for datadaog
|
@g-marius do you use something like Flux or ArgoCD? |
I believe the fix is released already as part of 0.24.0 |
Keeping the POD annotations is essential to run the workload in EKS, where the fargate profile is the default one.
Dropping essential annotations, such as
"eks.amazonaws.com/compute-type" = "ec2"
will cause the POD to be unschedulable due to the fact that:Example manifest:
Interestingly, first POD of the 3 replicas starts with correct annotation, but then, the second doesn't as the annotations are dropped from the underlying statefulset.
Note that I also see this in the log of the operator, which is possibly the result of this behavior:
The text was updated successfully, but these errors were encountered: