Skip to content
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

Bumping apiVersion for healtchecks crd definition #1049

Merged
merged 1 commit into from
Apr 7, 2022

Conversation

tcinbis
Copy link
Contributor

@tcinbis tcinbis commented Mar 28, 2022

What this PR does / why we need it:

When deploying the healthchecks operator on the latest version of kind it will fail, because apiextensions.k8s.io/v1beta1 is not supported any longer.
This bumps the apiVersion to the stable version and adds minimal changes to adhere to the specification.

Which issue(s) this PR fixes:

Fixes #723

Special notes for your reviewer: -

Does this PR introduce a user-facing change?: No

@tcinbis tcinbis changed the title [Closes #723] Bumping apiVersion for healtchecks crd definition #723 Bumping apiVersion for healtchecks crd definition Mar 28, 2022
@tcinbis tcinbis changed the title #723 Bumping apiVersion for healtchecks crd definition Bumping apiVersion for healtchecks crd definition Mar 28, 2022
@sungam3r sungam3r requested a review from carlosrecuero March 28, 2022 21:53
@carlosrecuero
Copy link
Collaborator

Some potential problems to consider:

  • because of the fact that this piece is not versioned, this will break for everyone that was using the previous version and has an old kubernetes version --> My proposal is to rename the previous version for them and add a quick comment on the readme.
  • check that the operator executable is taking the new version and, if required, create a new version of it.

@tcinbis
Copy link
Contributor Author

tcinbis commented Mar 29, 2022

Hey @carlosrecuero,

Thanks for the feedback! I have two clarification questions before I go and add more changes.

  1. With renaming you suggest adding an old copy of the deploy/operator/crd/healthcheck-crd.yaml under a different name (e.g. deploy/operator/crd/healthcheck-crd-pre-v1.22.yaml)?
  2. We are only applying the YAML files are not using the installer. Could you or someone else take on the testing of it? :)

Thanks!

@carlosrecuero
Copy link
Collaborator

Hey @carlosrecuero,

Thanks for the feedback! I have two clarification questions before I go and add more changes.

  1. With renaming you suggest adding an old copy of the deploy/operator/crd/healthcheck-crd.yaml under a different name (e.g. deploy/operator/crd/healthcheck-crd-pre-v1.22.yaml)?
  2. We are only applying the YAML files are not using the installer. Could you or someone else take on the testing of it? :)

Thanks!

  1. Ok
  2. Let's split it, it is ok.

When deploying the healthchecks operator on the latest version of `kind` it will fail, because `apiextensions.k8s.io/v1beta1` is not supported any longer.
This bumps the `apiVersion` to the stable version and adds minimal changes to adhere to the specification.

Also adding a copy of the pre v1.22 CRD.
@tcinbis
Copy link
Contributor Author

tcinbis commented Apr 5, 2022

Hey @carlosrecuero and @sungam3r !
I added the pre v1.22 version of the CRD to the PR. I think from my side we are ready to go.
What do you think? :)

@sungam3r
Copy link
Collaborator

sungam3r commented Apr 7, 2022

I do not use/understand this part of project, waiting for @carlosrecuero .

@carlosrecuero
Copy link
Collaborator

Sorry for the delay. Approved.

@tcinbis
Copy link
Contributor Author

tcinbis commented Apr 7, 2022

Awesome thanks! I can’t merge since I am missing write access, so I guess someone of you will press the button? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update CRD apiVersion to apiextensions.k8s.io/v1
3 participants