请问是否有ECS自建部署k8s 集群后（非部署前），集成 Alibaba Cloud Provider 最佳实践 about cloud-provider-alibaba-cloud HOT 10 CLOSED

已更新文档，见 #225
对于已部署集群，需要先为集群中节点添加ProviderID kubectl patch node ${NODE_NAME} -p "{\"spec\":{\"providerID\": ${NODE_NAME} }}" , 然后按照Install Alibaba CloudProvider support 后续步骤进行按照。

from cloud-provider-alibaba-cloud.

已更新文档，见 #225
对于已部署集群，需要先为集群中节点添加ProviderID kubectl patch node ${NODE_NAME} -p "{\"spec\":{\"providerID\": ${NODE_NAME} }}" , 然后按照Install Alibaba CloudProvider support 后续步骤进行按照。

如果是自己更改过ecs主机名呢：
[root@master cloud-balancer]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master Ready master 15d v1.18.6
node1 Ready worker 15d v1.18.6
node2 Ready worker 15d v1.18.6
providerID是用自己改后的主机名，还是按照默认的格式：cn-hangzhou.i-bp1ai7mtngada8f1ud72

from cloud-provider-alibaba-cloud.

已更新文档，见 #225
对于已部署集群，需要先为集群中节点添加ProviderID kubectl patch node ${NODE_NAME} -p "{\"spec\":{\"providerID\": ${NODE_NAME} }}" , 然后按照Install Alibaba CloudProvider support 后续步骤进行按照。

如果是自己更改过ecs主机名呢：
[root@master cloud-balancer]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master Ready master 15d v1.18.6
node1 Ready worker 15d v1.18.6
node2 Ready worker 15d v1.18.6
providerID是用自己改后的主机名，还是按照默认的格式：cn-hangzhou.i-bp1ai7mtngada8f1ud72

providerID是固定格式[region-id].[instance-id]

from cloud-provider-alibaba-cloud.

同求

from cloud-provider-alibaba-cloud.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from cloud-provider-alibaba-cloud.

请问按照这个流程处理完的集群，再添加节点的时候需要进行什么操作吗？

from cloud-provider-alibaba-cloud.

请问按照这个流程处理完的集群，再添加节点的时候需要进行什么操作吗？

尝试了一下，只需要做 patch 这一步操作就行

from cloud-provider-alibaba-cloud.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from cloud-provider-alibaba-cloud.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

from cloud-provider-alibaba-cloud.

@k8s-triage-robot: Closing this issue.

from cloud-provider-alibaba-cloud.