External kubernetes dependencies

[feiskyer]

This is the meta-issue for tracking all the external dependencies, which are blockers for full standalone azure cloud provider.

cross reference KEP for out-of-tree Azure cloud provider.

API throttling

Instance metadata service could help to reduce API throttling issues, and increase the nodes initialization duration. This is especially helpful for large clusters.

But with CCM, this is not possible anymore because the above functionality has been moved to cloud controller manager. We should add this back into Kubelet.

This issue is being tracked under kubernetes/cloud-provider#30 and the KEP for supporting IMDS is kubernetes/enhancements#1158.

Credential provider

Azure credential provider is still required (set by kubelet --azure-container-registry-config)

• On tracking at Deprecate --azure-container-registry-config kubernetes/kubernetes#58034
• Being tracked under Extracting/Migrating the Credential Provider: KEP + Alpha Implementation kubernetes/cloud-provider#13.
• KEP Credential provider extraction kubernetes/enhancements#1406

AzureDisk and AzureFile CSI drivers

AzureDisk and AzureFile volume plugins are still in-tree, but even with --external-cloud-volume-plugin=azure configured on kube-controller-manager, AzureDisk and AzureFile are still not working. See kubernetes/kubernetes#71018 for explanations.

So to use with CCM, CSI drivers should always be used. The CSI drivers for them are tracking on the separate repos:

• https://github.com/kubernetes-sigs/azuredisk-csi-driver
• https://github.com/kubernetes-sigs/azurefile-csi-driver

1. CSI on Windows (alpha in k8s v1.18) (in progress)

• make azure disk CSI driver work on Windows
• make azure file CSI driver work on Windows

2. CSI Driver Migration (in-tree driver to CSI driver) (alpha in k8s v1.18) (in progress)

• azure disk CSI Driver Migration
• azure file CSI Driver Migration

3. CSI drivers support on Windows

• azure disk CSI driver on Windows
• azure file CSI driver on Windows

4. CSI driver integration with aks-engine (done)

• Deploy CSI drivers for AzureDisk/AzureFile for cloud-controller-manager

[justaugustus]

/assign

[feiskyer]

To support production-level out-of-tree Azure cloud provider, API throttling issue is a hard-blocker. So we need a new proposal to make CCM support instance metadata (refer kubernetes/cloud-provider#30).

/milestone v1.16

[k8s-ci-robot]

@feiskyer: The provided milestone is not valid for this repository. Milestones in this repository: [v1.14, v1.15]

Use /milestone clear to clear the milestone.

In response to this:

To support production-level out-of-tree Azure cloud provider, API throttling issue is a hard-blocker. So we need a new proposal to make CCM support instance metadata (refer kubernetes/cloud-provider#30).

/milestone v1.16

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.

[feiskyer]

Status update:

• Credential provider extraction kubernetes/enhancements#1406 is working on the KEP for Credential Provider Extraction
• KEP: Support Instance Metadata Service with Cloud Controller Manager kubernetes/enhancements#1158 has been integrated with aks-engine for v1.16+ cluster

[craiglpeters]

kubernetes/enhancements#1406 is the new KEP for Credential Provider Extraction

[craiglpeters]

/milestone clear
/milestone v1.19

[craiglpeters]

/milestone v1.19

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[craiglpeters]

/milestone clear

[craiglpeters]

/milestone v1.20

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale