-
Notifications
You must be signed in to change notification settings - Fork 344
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
Operation cannot be fulfilled on deployments.apps... #927
Comments
Yes, I'll take a look. |
@jpkrohling is this still an issue? Or was fixed via #940 ? |
I believe this was fixed. |
Hi, I am still getting this error 'Operation cannot be fulfilled on deployments.apps'. I have used auto side car injection as given in the example, deploy/examples/business-application-injected-sidecar.yaml. |
@SS30723 I am also facing same issue... and doing exactly same what you have done. have you got nay resolution in it.. @jpkrohling I am also getting below error while deploying sample application (business-application-injected-sidecar.yaml) . I am able to view jaeger-query service in UI. but this service is not appearing in UI.. This is what I have got in operator log. however I could see 2/2 container running in sample application pod. But the service is not appearing in jaeger UI error msg="failed to update deployment with sidecar" error="Operation cannot be fulfilled on deployments.apps "myapp": the object has been modified; please apply your changes to the latest version and try again" jaeger=jaeger-kafka-poc jaeger-namespace=observability name=myapp namespace=observability |
Having same problem - jaeger-operator v1.28.0. Upgraded yesterday to fix a few other bugs we had with correct collector selection in sidecar injector. Now none of our deployments get injected with latest version of jaeger-agent. |
Having same problem - jaeger-operator v1.36.0. Yesterday was updated along with the cluster components. Previously on v1.35.0 there were no problems. Reverting the version didn't fix the problem |
While testing #914, I saw a message similar to the following in the logs. Trying it out with the latest master confirms that this exists there as well:
This can be reproduced by deploying our example
deploy/examples/business-application-injected-sidecar.yaml
:jaeger-operator/deploy/examples/business-application-injected-sidecar.yaml
Lines 1 to 23 in d80bd24
@rubenvp8510 would you be able to look into this one?
The text was updated successfully, but these errors were encountered: