Closed samof76 closed 1 year ago
Notice the failures in this job as well... https://github.com/spotahome/redis-operator/actions/runs/4089636238/jobs/7052491278
@ese Can you please check this?
@Wouter0100 is this something you are also running into?
Not yet really
@Wouter0100 / @ese do you know is there a way we could disable the alpha fields while generating the crds? I have been looking for this... if you guys already know i could just add it to the Makefile
@samof76 according to this issue https://github.com/kubernetes-sigs/controller-tools/issues/600 it seems we have to come up with some sort of a workaround. I didn't find any flags/keys or whatever for controller-gen to prevent it from generating a crd witht alpha fields. Right now, I'm thinking of a recursive yaml parser for pruning based on description containing "This field is alpha-level". The question that is teasing me is how it worked before..
There is dependabot PR that upgraded the api and apimachinery to 26 version. And introduced this regression. I have rolled back that changes in my feature for custom probes. But I think now the minikube github actions seems to be broken 😞
@miklezzzz
A couple of things I have done fix... ... 1. The issue of the alpha fields. Downgraded k8s.io/api and k8s.io/apimachinery
go get -v k8s.io/api@v0.24.4
go get k8s.io/apimachinery@v0.24.4
go mod tidy
go mod vendor
And then generated CRD file.
... 2. The minikube new version has an issue with the cni plugin so downgraded it, as well.
@samof76 Also bumped into minikube 1.29.0 cni issue :( p.s. for disabling alpha fields this may come in handy or not:
- name: Install feature gate filter
run: go get github.com/miklezzzz/k8sfeaturegatefilter && go install github.com/miklezzzz/k8sfeaturegatefilter
- name: Add redisfailover CRD after sanitazing
run: ~/go/bin/k8sfeaturegatefilter -file manifests/databases.spotahome.com_redisfailovers.yaml -gates DynamicResourceAllocation | kubectl create -f -
@miklezzzz thanks. I see there a lot of PR still pending. I am not sure if there is some issue with the upstream folks.
This issue is stale because it has been open for 45 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Expected behaviour
Generating the CRD, and replacing should pass without any failures
Actual behaviour
Now it fails with the following error...
Steps to reproduce the behaviour
Describe step by step what you've have done to get to this point
Environment
How are the pieces configured?
Logs