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

⚠️ Add v1alpha7 #1497

Merged
merged 2 commits into from
Mar 3, 2023
Merged

⚠️ Add v1alpha7 #1497

merged 2 commits into from
Mar 3, 2023

Conversation

mdbooth
Copy link
Contributor

@mdbooth mdbooth commented Feb 28, 2023

Add a new v1alpha7 API version in anticipation of breaking API changes.

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 28, 2023
@netlify
Copy link

netlify bot commented Feb 28, 2023

Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name Link
🔨 Latest commit 346b625
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/6401e42741975300081805c8
😎 Deploy Preview https://deploy-preview-1497--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 28, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mdbooth

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 28, 2023
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 28, 2023
@mdbooth
Copy link
Contributor Author

mdbooth commented Feb 28, 2023

/test pull-cluster-api-provider-openstack-e2e-full-test

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 1, 2023

/test pull-cluster-api-provider-openstack-e2e-full-test

Copy link
Contributor

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!
One nit below, and one question: Should we change the clusterctl upgrade test to initialize with v1alpha6 instead of v1alpha5 now?
Ref:

@@ -1,5 +1,5 @@
/*
Copyright 2022 The Kubernetes Authors.
Copyright 2021 The Kubernetes Authors.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure where this came from. Maybe change it to 2023 instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That will be after I deleted it and then copied it from elsewhere after realising that was a mistake 😂

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 2, 2023

Looks good! One nit below, and one question: Should we change the clusterctl upgrade test to initialize with v1alpha6 instead of v1alpha5 now? Ref:

I would defer this to you. We could:

  • Leave it alone (test v1alpha5->v1alpha7)
  • Update it to v1alpha6 (test v1alpha6->v1alpha7)
  • Add a second test and do both

@lentzi90
Copy link
Contributor

lentzi90 commented Mar 2, 2023

I would defer this to you. We could:

* Leave it alone (test v1alpha5->v1alpha7)

* Update it to v1alpha6 (test v1alpha6->v1alpha7)

* Add a second test and do both

Probably the nicest thing would be to add a second test and test both. But I would say it is more important to have v1alpha6 -> v1alpha7.

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 2, 2023

/test pull-cluster-api-provider-openstack-e2e-full-test

Copy link
Contributor

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2023
@lentzi90
Copy link
Contributor

lentzi90 commented Mar 3, 2023

Ah missed that the e2e-full test was failing...
It is because the e2e config is missing the v0.7.1 release that it is trying to use now. Basically the v0.6.4 section can be replaced with v0.7.1 here
https://github.com/shiftstack/cluster-api-provider-openstack/blob/28533e5a2b06d703781678f606507f3f64c66bf7/test/e2e/data/e2e_conf.yaml#L77-L91

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2023
@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

/test pull-cluster-api-provider-openstack-e2e-full-test

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

Ah missed that the e2e-full test was failing... It is because the e2e config is missing the v0.7.1 release that it is trying to use now. Basically the v0.6.4 section can be replaced with v0.7.1 here https://github.com/shiftstack/cluster-api-provider-openstack/blob/28533e5a2b06d703781678f606507f3f64c66bf7/test/e2e/data/e2e_conf.yaml#L77-L91

Thanks! I've added a second section. Is that going to work?

@lentzi90
Copy link
Contributor

lentzi90 commented Mar 3, 2023

Having both v0.6.4 and v0.7.1 is perfectly fine, but now I see two sections with v0.7.99. Not sure how that will go 🤔

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

Having both v0.6.4 and v0.7.1 is perfectly fine, but now I see two sections with v0.7.99. Not sure how that will go 🤔

🤦

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

/test pull-cluster-api-provider-openstack-e2e-full-test

Copy link
Contributor

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2023
Copy link
Member

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, only one nit I could notice is missing the API types update in the doc: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/main/docs/book/src/clusteropenstack/configuration.md

@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

I'll let this -full test complete before pushing a docs update. Assuming everything is ok I won't bother running it again.

@furkatgofurov7
Copy link
Member

I'll let this -full test complete before pushing a docs update. Assuming everything is ok I won't bother running it again.

@mdbooth makes sense 🙂
Although I see pull-cluster-api-provider-openstack-e2e-test is run in every and each PR which does not really makes sense to me (i.e for only doc update changes in #1500).
We could add run_If_changed on at least ^ e2e presubmit job (example: https://github.com/kubernetes/test-infra/blob/464e4bbc73d0934491fb285eca8719e22a173adc/config/jobs/kubernetes-sigs/cluster-api/cluster-api-presubmits-release-1-3.yaml#L125) to ensure it is not run if only e.g. documentation is changed.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2023
@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

Only change is updating the api version refs in the docs.

Copy link
Contributor

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2023
Copy link
Member

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Not sure if the repo has requirements for the PR labels, but this is generally should be labelled as ⚠️ change to me.

@mdbooth mdbooth changed the title ✨ Add v1alpha7 ⚠️ Add v1alpha7 Mar 3, 2023
@mdbooth
Copy link
Contributor Author

mdbooth commented Mar 3, 2023

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 3, 2023
@k8s-ci-robot k8s-ci-robot merged commit c06146b into kubernetes-sigs:main Mar 3, 2023
@mdbooth mdbooth deleted the v1alpha7 branch March 3, 2023 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants