We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2024-06-20T22:05:13.061Z ERROR 7 --- [nio-8080-exec-2] o.a.c.c.C.[.[.[.[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [/api] threw exception [Request processing failed: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: PATCH at: https://10.233.0.1:443/api/v1/namespaces/user-tm8enk/secrets/sh.onyxia.release.v1.vscode-python-614051?fieldManager=fabric8. Message: metadata.managedFields must be nil. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=metadata.managedFields must be nil, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}).] with root cause io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: PATCH at: https://10.233.0.1:443/api/v1/namespaces/user-tm8enk/secrets/sh.onyxia.release.v1.vscode-python-614051?fieldManager=fabric8. Message: metadata.managedFields must be nil. Received status: Status(apiVersion=v1, code=400
It seems that we are using serverSideApply but I don't understand this choice regarding to this documentation
https://kubernetes.io/docs/reference/using-api/server-side-apply/#conflicts
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
It seems that we are using serverSideApply but I don't understand this choice regarding to this documentation
https://kubernetes.io/docs/reference/using-api/server-side-apply/#conflicts
The text was updated successfully, but these errors were encountered: