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 Calico v3.17.3 and v3.18.1 #7524

Merged
merged 4 commits into from
Apr 21, 2021

Conversation

cristicalin
Copy link
Contributor

@cristicalin cristicalin commented Apr 18, 2021

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

This PR adds the necessary hashes to support Calico versions 3.17 and 3.18 (while bumping the default to 3.17.3).

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

The release notes for versions 3.17 and 3.18 compared to the aging 3.16 are long so I include just the links here:

Does this PR introduce a user-facing change?:

Upgrade default calico network plugin to version 3.17.3

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 18, 2021
@k8s-ci-robot k8s-ci-robot requested review from bozzo and EppO April 18, 2021 16:30
@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 18, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @cristicalin. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 18, 2021
@champtar
Copy link
Contributor

I'm not following calico closely but why not 3.18.1 ?

@cristicalin
Copy link
Contributor Author

cristicalin commented Apr 18, 2021

My rationale was to add that in a separate PR to keep review effort focused on 1 change at a time.

I added the hashes for 3.18.1 as well in a separate commit but kept the default to 3.17.3 unless you think I should bump the default to 3.18.1 as well.

One thing that I'm not fully sure is if to go from 3.16.9 to 3.18.1 we would need to go through 3.17.3 as an interim version, I have to do some testing in that area.

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 18, 2021
@cristicalin cristicalin changed the title Calico v3.17.3 Add Calico v3.17.3 and v3.18.1 Apr 18, 2021
Copy link
Member

@floryut floryut left a comment

Choose a reason for hiding this comment

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

/ok-to-test

Fine to upgrade only to 3.17.3, we could always bump to 3.18.x later on

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 19, 2021
@cristicalin
Copy link
Contributor Author

I have a suspicion that the CI failure is unrelated (markdown job failed in a git fetch), could you re-trigger it?

@champtar
Copy link
Contributor

Relaunched, kubespray CI always need a bit of love to pass :P

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 20, 2021
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 20, 2021
@cristicalin
Copy link
Contributor Author

This time the issue was with Calico 3.17 and newer crd files missing the --- yaml separator. I fixed this and tested both 3.17.3 and 3.18.1 deployments.

It turns out my hash for the 3.18 archive was also wrong so I also fixed it.

@floryut can you bless another CI run?

@floryut
Copy link
Member

floryut commented Apr 20, 2021

This time the issue was with Calico 3.17 and newer crd files missing the --- yaml separator. I fixed this and tested both 3.17.3 and 3.18.1 deployments.

It turns out my hash for the 3.18 archive was also wrong so I also fixed it.

@floryut can you bless another CI run?

CI is running right now, no error for now 🙏

@cristicalin
Copy link
Contributor Author

Again last failure seems unrelated to this change.

@@ -119,12 +119,13 @@
-e '/^\s{2,4}annotations:/{:1;/\(devel\)$/!{N;b 1}; /.*/d}'
{{ local_release_dir }}/calico-{{ calico_version }}-kdd-crds/*.yaml
when:
- calico_version is version('v3.17.0', '<')
- calico_version is version('v3.19.0', '<')
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you sure about this one ?
I think those annotations are not present in 3.17+

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Indeed, I looked over the CRDs from 3.17 and 3.18 and they were not there. I just assumed that since there was no other mention of 3.17 before this patch that when condition was an upper bound. That said, the command itself is harmless since it will not change anything in the 3.17+ CRD files but I removed the unnecessary change anyway.

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree it's harmless but in kubespray we tend to carry workaround for way longer than needed, once we remove the 3.17 hash we can also remove this task ;)

@champtar
Copy link
Contributor

/cc @champtar

@k8s-ci-robot k8s-ci-robot requested a review from champtar April 21, 2021 14:15
Copy link
Contributor

@champtar champtar left a comment

Choose a reason for hiding this comment

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

see previous message

@cristicalin cristicalin force-pushed the calico_v3.17.3 branch 2 times, most recently from 4ba1a43 to 72a809c Compare April 21, 2021 14:54
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: champtar, cristicalin, floryut

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

@champtar
Copy link
Contributor

we will have to wait for #7535 to get merged and maybe need rebase

@cristicalin
Copy link
Contributor Author

Rebased after #7535 was merged as requested.

@champtar
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 21, 2021
@k8s-ci-robot k8s-ci-robot merged commit add6186 into kubernetes-sigs:master Apr 21, 2021
@champtar
Copy link
Contributor

you forgot to update the README

unai-ttxu pushed a commit to unai-ttxu/kubespray that referenced this pull request May 18, 2021
* add hashes for calico v3.17.3

* add hashes for claico v3.18.1

* bump default calico version to v3.17.3

* calico crds are missing yaml separator breaking kdd
unai-ttxu added a commit to Stratio/kubespray that referenced this pull request May 18, 2021
* Add Calico v3.17.3 and v3.18.1 (kubernetes-sigs#7524)

* add hashes for calico v3.17.3

* add hashes for claico v3.18.1

* bump default calico version to v3.17.3

* calico crds are missing yaml separator breaking kdd

* Calico new versions v3.17.4 and v3.18.2 (kubernetes-sigs#7563)

* calico: upgrade from v3.17.3 to v3.17.4

* calico: upgrade from v3.18.1 to v3.18.2

* Fixes issue kubernetes-sigs#7573 - Made Calico permissions compatible with v3.18.x (see projectcalico/calico#4557).  Specifically, granted watch to custom resources blockaffinities, ipamblocks & ipamhandles (kubernetes-sigs#7575)

* bump calico 3.18 to v3.18.3 (kubernetes-sigs#7592)

* Support Calico advertisement of MetalLB LoadBalancer IPs (kubernetes-sigs#7593)

* add initial MetalLB docs

* metallb allow disabling the deployment of the metallb speaker

* calico>=3.18 allow using calico to advertise service loadbalancer IPs

* Document the use of MetalLB and Calico

* clean MetalLB docs

Co-authored-by: Cristian Calin <[email protected]>
Co-authored-by: holmesb <[email protected]>
LuckySB pushed a commit to southbridgeio/kubespray that referenced this pull request Jun 12, 2021
* add hashes for calico v3.17.3

* add hashes for claico v3.18.1

* bump default calico version to v3.17.3

* calico crds are missing yaml separator breaking kdd
sakuraiyuta pushed a commit to sakuraiyuta/kubespray that referenced this pull request Apr 16, 2022
* add hashes for calico v3.17.3

* add hashes for claico v3.18.1

* bump default calico version to v3.17.3

* calico crds are missing yaml separator breaking kdd
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. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants