Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd calico 3.7.3 support #4953
Conversation
This comment has been minimized.
This comment has been minimized.
Welcome @jlacoline! |
This comment has been minimized.
This comment has been minimized.
ci check this |
env: | ||
{% if calico_datastore == "kdd" and calico_version is version('v3.6.0', '>=') %} |
This comment has been minimized.
This comment has been minimized.
AlexeyKasatkin
Jul 9, 2019
Contributor
Does kube-controllers work for you? I had to change 'calico-kube-controllers' ClusterRole according to calico manifest to make it work properly.
This comment has been minimized.
This comment has been minimized.
jlacoline
Jul 9, 2019
•
Author
Contributor
I actually did forgot this part, and did not detect it in my deployment because the cluster role got updated as a side effect of other tests.
Fixed by latest commit
This comment has been minimized.
This comment has been minimized.
AlexeyKasatkin
Jul 9, 2019
Contributor
Thanks. Although, here and in the latest commit there are conditionals that prevent us from running calico+kdd for calico < v3.6 at all. So, those conditionals should be changed or it should be some formal restriction to prevent user from installing calico <v3.6 using kdd.
This comment has been minimized.
This comment has been minimized.
jlacoline
Jul 9, 2019
Author
Contributor
In the latest commit I added the calico-version >= 3.6
limitation because no cluster role is defined for kube-controller in previous versions in kdd mode (I looked at 3.4 and 3.5 templates).
I used the same reasoning for the other parts in this PR that have a constraint on calico_version
.
So in this regard there should be no regression concerning previous versions.
This comment has been minimized.
This comment has been minimized.
AlexeyKasatkin
Jul 9, 2019
•
Contributor
Agree. Sorry, I didn't check that.
Seems, it would be better to exclude whole calico-kube-controllers Deployment from installation for calico < v3.6 using kdd
then.
This comment has been minimized.
This comment has been minimized.
jlacoline
Jul 9, 2019
Author
Contributor
Apparently calico kube controller seems irrelevant when kdd mode is used in versions < 3.6 so I did as you suggested (commit d988cca).
I can remove this commit if this technical choice isn't approved by everybody
This comment has been minimized.
This comment has been minimized.
/lgtm |
This comment has been minimized.
This comment has been minimized.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlacoline, mattymo 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 |
This comment has been minimized.
This comment has been minimized.
/lgtm |
20c7e31
into
kubernetes-sigs:master
This comment has been minimized.
This comment has been minimized.
@holmsten @jlacoline README.md needs to be updated since 3.4.0 is not default anymore. |
* Add calico 3.7.3 support * add calico_datastore variable to policy controller role * add missing clusterrole rules for calico policy controller * disable calico kube controller when kdd mode is used for versions < 3.6
* Add calico 3.7.3 support * add calico_datastore variable to policy controller role * add missing clusterrole rules for calico policy controller * disable calico kube controller when kdd mode is used for versions < 3.6
jlacoline commentedJul 8, 2019
What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds support for calico version up to 3.7.3 (current max version is 3.4.4)
Special notes for your reviewer:
I made the templates as close as possible to calico installation manifests from here: https://docs.projectcalico.org/v3.7/getting-started/kubernetes/installation/calico
I were also inspired by the calico helm templates: https://github.com/projectcalico/calico/tree/master/_includes/v3.7/charts/calico/templates
Does this PR introduce a user-facing change?: