configuration update to v1.7.8 #1335
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jayanthvn
reviewed
Dec 16, 2020
config/v1.7/calico.yaml
Outdated
| @@ -32,7 +32,12 @@ spec: | |||
| # container programs network policy and routes on each | |||
| # host. | |||
| - name: calico-node | |||
| image: quay.io/calico/node:v3.15.1 | |||
There was a problem hiding this comment.
Why do we have calico config changes?
There was a problem hiding this comment.
We should have calico copied from master to v1.7. Seems we didn't do that in previous release?
There was a problem hiding this comment.
Master/calico has some changes which needs to be merged to release-1.7. Changes will be merge to release-1.7 in the next release.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Configuration updates for v1.7.8 release
Which issue does this PR fix:
New release
What does this PR do / Why do we need it:
Update configuration files
If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
Does this change require updates to the CNI daemonset config files to work?:
No
Does this PR introduce any user-facing change?:
Yes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.