Closed rohit-dimagi closed 1 year ago
We have same issue.
EKS: 1.25
Helm Chart Version
Datadog-operator: 0.9.2
{"level":"ERROR","ts":"2023-03-10T17:33:35Z","logger":"setup","msg":"Problem running manager","error":"failed to wait for datadogagent caches to sync: no matches for kind \"PodDisruptionBudget\" in version \"
policy/v1beta1\""}
can we get some update on this or some workaround?
can we get some update on this or some workaround?
https://github.com/DataDog/datadog-operator/issues/734#issuecomment-1466571948
works for me with image 1.0.0-rc.10
and 1.0.0-rc.12
for a two weeks stable enough. We're waiting for GA of 1.0
When I try to use the fixed images
docker pull gcr.io/datadoghq/operator:1.0-pre-10 Error response from daemon: manifest for gcr.io/datadoghq/operator:1.0-pre-10 not found: manifest unknown: Failed to fetch "1.0-pre-10" from request "/v2/datadoghq/operator/manifests/1.0-pre-10".
docker pull gcr.io/datadoghq/operator:1.0-pre-12 Error response from daemon: manifest for gcr.io/datadoghq/operator:1.0-pre-12 not found: manifest unknown: Failed to fetch "1.0-pre-12" from request "/v2/datadoghq/operator/manifests/1.0-pre-12".
docker pull gcr.io/datadoghq/operator:1.0-pre-12 Error response from daemon: manifest for gcr.io/datadoghq/operator:1.0-pre-12 not found: manifest unknown: Failed to fetch "1.0-pre-12" from request "/v2/datadoghq/operator/manifests/1.0-pre-12".
I'm very sorry for mistake :( correct image tag is 1.0.0-rc.12
Thanks, we also need --set datadogCRDs.migration.datadogAgents.version=v2alpha1 ?
yes
hi all - I see this is closed but I want to make sure everyone is all set. 1.0 was released a few weeks ago, did you get a chance to try it @ij3net? @walter-heestermans-toyota, are you all set with the flag?
We tried to document this migration in the chart and in the main repo, I hope this will suffice but if you have any feedback please let us know.
hi all - I see this is closed but I want to make sure everyone is all set. 1.0 was released a few weeks ago, did you get a chance to try it @ij3net? @walter-heestermans-toyota, are you all set with the flag?
Thank you very much for notice. I've upgraded our configuration up to 1.0.2 chart version and it's works like a charm.
Describe what happened: Datadog-Operator is throwing error after upgrade to kubernetes V1.25.
policy/v1beta1
forPodDisruptionBudget
has been replaced in new version. and i'm running withreplicacout: 1
Installed CRDs areDescribe what you expected: Operator pods should start normally
Additional environment details (Operating System, Cloud provider, etc):
EKS: 1.25
Helm Chart VersionDatadog-operator: 0.9.2
Datadog: 3.10.6