-
Notifications
You must be signed in to change notification settings - Fork 33
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
CRD issue for Kubernetes v1.18+ #260
Comments
Is this the source of failures in #257 ? |
Doesn't look like it. The E2E logs in GitHub Actions for #257 shows this when installing the CRD's:
Unfortunately I don't have time to dig through the logs for #257 today. |
Fixed as part of #259. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of #259 I stumbled upon a problem with controller-gen which looks like it is related to kubernetes-sigs/controller-tools#444. Seems like there's not a newer build available for controller-gen right now that fixes the problem for us. I did try upgrading controller-gen from v0.3.0 to v0.4.0 locally and it does seem to use the stable API for the CRD objects instead of the v1beta1 API, but the same problem persists.
Until now we've been using the image
kindest/node:v1.17.11
for localkind
tests but the GitHub Action workflow pulls in a newer version when running E2E tests (kindest/node:v1.19.1
) which is failing to accept our CRD for the HumioCluster resource (after the changes in #259) when runningkubectl apply -f ....
to install it. I did a bit more testing, and this is what I found:kindest/node:v1.18.8
& branch for #259:kindest/node:v1.19.1
& branch for #259:Upgrading controller-gen seems to work, but there's currently not a release that includes this fix yet.
The text was updated successfully, but these errors were encountered: