-
Notifications
You must be signed in to change notification settings - Fork 208
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
Hooks incorrectly watch different apiVersions with the same Kind #306
Comments
Hello! The behavior you've described is correct. In short, It's not an issue inside the shell-operator but a result of the machinery inside Kubernetes. Here is the link that explains version handling for CRDs: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/ |
context
We have two different apiVersions for our aurora dababase crds:
And have two startup.sh for both
v1beta1
&v1beta2
, but in different folder.Take
v1beta2
ofstandup.sh
details as below:Expected behavior (what you expected to happen):
As we have to support 2 versions for our operator, we expected:
Kind
v1beta1
hooks could only watch the apiVersion ofaurora.rds.cloud/v1beta1
.v1beta2
hooks could only focus on apiVersion ofaurora.rds.cloud/v1beta2
Actual behavior (what actually happened):
Kind
v1beta1
hooks watch bothv1beta1
&v1beta2
resourcev1beta2
hooks watch bothv1beta1
&v1beta2
resourceeg:
delete-postgres-v1beta2
->aurora.rds.cloud/v1beta2
Error outputs as below:
Correct outputs as below:
If the hooks config with the same
Kind
but differentapiVersion
:context::jq -r '.'
could return the incorrect apiVersion as above ☝️Environment:
The text was updated successfully, but these errors were encountered: