chore: Update calico manifests to v3.4.0#311
chore: Update calico manifests to v3.4.0#311song-jiang wants to merge 3 commits intoAzure:masterfrom
Conversation
|
💖 Thanks for opening your first pull request! 💖 We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix. Examples of commit messages with semantic prefixes: - |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: song-jiang If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
a032a11 to
567b0d1
Compare
567b0d1 to
dd0206a
Compare
Codecov Report
@@ Coverage Diff @@
## master #311 +/- ##
=======================================
Coverage 53.16% 53.16%
=======================================
Files 95 95
Lines 14244 14244
=======================================
Hits 7573 7573
Misses 6006 6006
Partials 665 665 |
|
Hi @song-jiang I found a lot of uneeded indenting in the yaml you updates, .i.e: The dash |
| "nodename": "__KUBERNETES_NODE_NAME__", | ||
| "mtu": 1500, | ||
| "ipam": <calicoIPAMConfig>, | ||
| "ipam" : <calicoIPAMConfig>, |
There was a problem hiding this comment.
Thanks @sylr for the review. The manifests has been auto generated for aks-engine from a calico manifest. I will fix the script to output a better format.
| metadata: | ||
| labels: | ||
| k8s-app: calico-typha | ||
| addonmanager.kubernetes.io/mode: "EnsureExists" |
There was a problem hiding this comment.
If you remove this the addon-manager won't create the object.
There was a problem hiding this comment.
From my test, I can see calico-typha pod running by just having label addonmanager.kubernetes.io/mode: "EnsureExists" set at Deployment metadata layer. This is similar to Deployment calico-typha-horizontal-autoscaler below.
So I am thinking omitting this label for template.metadata should be fine. WDYT?
There was a problem hiding this comment.
You're right 👍 I missed that it was not in the good section
|
@sylr Could you review it again? I have addressed all your comments. |
| apiVersion: extensions/v1beta1 | ||
| kind: Deployment | ||
| apiVersion: policy/v1beta1 | ||
| kind: PodDisruptionBudget |
There was a problem hiding this comment.
You should not include the PodDisruptionBudget object. It was added at a time but was removed because it provoked problems with the upgrade problem (see #300).
Also a PodDisruptionBudget can not be updated at the moment. It needs to be removed and recreated if you want to change the spec so it's better to not include it.
| # the master to communicate with pods. | ||
| - effect: NoSchedule | ||
| operator: Exists | ||
| # Make sure calico-node gets scheduled on all nodes. |
There was a problem hiding this comment.
Please align all array items comments with the -
There was a problem hiding this comment.
Fixing comment indentations by a script seems to be much harder. Let me try and come back to you later.
There was a problem hiding this comment.
I fixed indentation manually. Will update script later. @sylr Please have another look. Thanks.
3e08e20 to
1aeb1c9
Compare
|
@sylr Could you help with another look? |
|
@sylr Have you got chance to review my latest change? |
|
@song-jiang sorry but I've been really overwhelmed at work recently. I don't think I'll have the time to review it more in the following days. |
|
@sylr No worries. Thanks for update. |
|
Close this PR since I am going to raise PR with calico 3.5 |
Reason for Change:
This PR updates calico manifests to v3.4.0
Issue Fixed:
None
Requirements:
Notes:
None.