-
Notifications
You must be signed in to change notification settings - Fork 276
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
Use deployment for CCM in example yaml #1252
Use deployment for CCM in example yaml #1252
Conversation
- name: etc-ssl | ||
mountPath: /etc/ssl | ||
readOnly: true | ||
hostPath: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These files can not be found..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't change this part. Do you mean there's some problem with the original yaml file about these files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are ca certs used by apiserver and other component. These files are located on master.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think toleration has been set for master?
https://github.com/kubernetes-sigs/cloud-provider-azure/pull/1252/files#diff-5f33bdfdadf384ba7fdac1e2fa8c83ad6d497f3c5f49fda1774def3b8c9f4115R153-R155
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add a nodeSelector
for master
- "--configure-cloud-routes=true" # "false" for Azure CNI and "true" for other network plugins | ||
- "--leader-elect=true" | ||
- "--route-reconciliation-period=10s" | ||
- "--v=2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we make v=4?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v=5 by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 4 is enough for debugging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use 4 for now and update in the future if needed.
- name: etc-kubernetes | ||
mountPath: /etc/kubernetes | ||
hostPath: | ||
path: /etc/kubernetes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we add a secret with azure.json and mount the secret for authz?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean we are going to put key-value pairs from azure.json
directly into this yaml file of a Secret
object? Like:
apiVersion: v1
kind: Secret
metadata:
name: azure-cloud-config
type: Opaque
stringData:
azure.json: |-
tenantId: <tenant-id>
subscriptionId: <subscription-id>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed offline. Updated.
site/content/en/install/azure-ccm.md
Outdated
@@ -39,6 +39,8 @@ Do not set flag `--cloud-provider`. | |||
|
|||
### azure-cloud-controller-manager | |||
|
|||
azure-cloud-controller-manager should be run as Deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
run as Deployment with multiple replicas or Kubelet static Pods on each master node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
could you update https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/tests/k8s-azure/manifest/cluster-api/vmss-multi-nodepool.yaml#L457 to deployment as well? |
fdf3f7a
to
a1970a7
Compare
5b46837
to
4436e44
Compare
path: /var/lib/waagent/ManagedIdentity-Settings | ||
--- | ||
apiVersion: v1 | ||
kind: Secret |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think capz should already create a secret, so we don't need to add it here? @nilo19 do you know the secret name, or host path should be used instead just for capz?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need a secret here in this template, and host path either. The capz will create a default one and the volume is defined in L533.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed offline. Since this yaml file is for capz, then keep it as it was.
Signed-off-by: Zhecheng Li <[email protected]>
4436e44
to
c2a84b2
Compare
apiVersion: v1 | ||
kind: Pod | ||
apiVersion: apps/v1 | ||
kind: Deployment | ||
metadata: | ||
name: cloud-controller-manager | ||
namespace: kube-system | ||
labels: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to keep the Deployment labels? I think defining pod labels (via spec.template.metadata.labels) should be sufficient.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is not a must but I think maybe we can keep it. It does no harm, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, keeping the deployment labels are not harmful
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feiskyer, lzhecheng 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 |
@lzhecheng: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/retest |
Signed-off-by: Zhecheng Li [email protected]
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: