You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created a controller with two helm charts helm-charts/v1alpha1 and helm-charts/v1alpha2 and a watches file with entries for both, then created a CR for just v1alpha1 but the controller runs both charts and keeps flipping between the two.
Hi @gbmeuk If you need to support multiple api's, you need to write a go operator so you can implement a conversion webhook to support the multiple apis. More on info on webhooks.
Hi @gbmeuk If you need to support multiple api's, you need to write a go operator so you can implement a conversion webhook to support the multiple apis. More on info on webhooks.
Thanks, @acornett21. I think Documentation may need clarifying for Helm as it's misleading to think the operator SDK will watch a version when it won't? Will the webhook approach work for Ansible Operator as well? In some testing with Ansible, I was looking to use standard Admission Webhooks to take the apiVersion from CREATE/UPDATE requests and add it as an annotation where Ansible could use that to decide whether to run a given role (CRD version) or not.
Bug Report
What did you do?
Created a controller with two helm charts
helm-charts/v1alpha1
andhelm-charts/v1alpha2
and a watches file with entries for both, then created a CR for just v1alpha1 but the controller runs both charts and keeps flipping between the two.Watches:
v1alpha1 chart just creates a namespace as:
v1alpha2 is slightly different
on the CRD, v1alpha1 is served and stored and v1alpha2 is just served.
What did you expect to see?
Just the v1alpha1 chart is ran with just these in the logs:
And the resources looking as:
What did you see instead? Under which circumstances?
Both charts are ran, and the resources flip between the attributes above and v1alpha2 ones:
Logs showing the upgrades and errors:
Environment
Operator type:
/language helm
Kubernetes cluster type:
GKE
Dockerfile:
Possible Solution
Haven't found anything obvious in code.
Additional context
N/A
The text was updated successfully, but these errors were encountered: