Skip to content
This repository was archived by the owner on Oct 24, 2023. It is now read-only.

chore: Update calico manifests to v3.4.0#311

Closed
song-jiang wants to merge 3 commits intoAzure:masterfrom
song-jiang:calico-v3.4-update
Closed

chore: Update calico manifests to v3.4.0#311
song-jiang wants to merge 3 commits intoAzure:masterfrom
song-jiang:calico-v3.4-update

Conversation

@song-jiang
Copy link
Contributor

@song-jiang song-jiang commented Jan 14, 2019

Reason for Change:

This PR updates calico manifests to v3.4.0

Issue Fixed:

None

Requirements:

Notes:
None.

@welcome
Copy link

welcome bot commented Jan 14, 2019

💖 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: - fix: change azure disk cachingMode to ReadOnly - feat: make maximumLoadBalancerRuleCount configurable - docs: add note on AKS-Engine and AKS relationship
Make sure to check out the developer guide for guidance on testing your change.

@msftclas
Copy link

msftclas commented Jan 14, 2019

CLA assistant check
All CLA requirements met.

@acs-bot
Copy link

acs-bot commented Jan 14, 2019

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: song-jiang
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mboersma

If they are not already assigned, you can assign the PR to them by writing /assign @mboersma in a comment when ready.

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

The pull request process is described here

Details 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

@song-jiang song-jiang changed the title Updated calico manifests to v3.4.0 chore: Update calico manifests to v3.4.0 Jan 14, 2019
@codecov
Copy link

codecov bot commented Jan 14, 2019

Codecov Report

Merging #311 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #311   +/-   ##
=======================================
  Coverage   53.16%   53.16%           
=======================================
  Files          95       95           
  Lines       14244    14244           
=======================================
  Hits         7573     7573           
  Misses       6006     6006           
  Partials      665      665

@sylr
Copy link
Contributor

sylr commented Jan 14, 2019

Hi @song-jiang I found a lot of uneeded indenting in the yaml you updates, .i.e:

array:
- item
- item2
array:
  - item
  - item2

The dash - of the array items should stay aligned with the name of the array.

"nodename": "__KUBERNETES_NODE_NAME__",
"mtu": 1500,
"ipam": <calicoIPAMConfig>,
"ipam" : <calicoIPAMConfig>,
Copy link
Contributor

Choose a reason for hiding this comment

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

Unneeded whitespace.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

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"
Copy link
Contributor

Choose a reason for hiding this comment

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

If you remove this the addon-manager won't create the object.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

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?

Copy link
Contributor

Choose a reason for hiding this comment

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

You're right 👍 I missed that it was not in the good section

@song-jiang
Copy link
Contributor Author

song-jiang commented Jan 16, 2019

@sylr Could you review it again? I have addressed all your comments.

apiVersion: extensions/v1beta1
kind: Deployment
apiVersion: policy/v1beta1
kind: PodDisruptionBudget
Copy link
Contributor

@sylr sylr Jan 16, 2019

Choose a reason for hiding this comment

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

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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please align all array items comments with the -

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixing comment indentations by a script seems to be much harder. Let me try and come back to you later.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I fixed indentation manually. Will update script later. @sylr Please have another look. Thanks.

@song-jiang
Copy link
Contributor Author

@sylr Could you help with another look?

@song-jiang
Copy link
Contributor Author

@sylr Have you got chance to review my latest change?

@sylr
Copy link
Contributor

sylr commented Jan 24, 2019

@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.

@song-jiang
Copy link
Contributor Author

@sylr No worries. Thanks for update.

@song-jiang
Copy link
Contributor Author

Close this PR since I am going to raise PR with calico 3.5

@song-jiang song-jiang closed this Feb 6, 2019
@song-jiang song-jiang deleted the calico-v3.4-update branch March 22, 2019 10:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants