Doc - Azure stack configuration with resourceManagerEndpoint

[rapsspider]

What happened:

I'm trying to add azure-csi on a kubernetes cluster in an azure stack environment. The [documentation] (https://cloud-provider-azure.sigs.k8s.io/install/configs/) states that an "azure.json" configuration file should contain the azure stack configuration.

With this configuration, I got no credentials provided for Azure cloud provider.

What you expected:

The documentation says that an "azure.json" file should contain information about the azure stack such as "ResourceManagerEndpoint" but it seems that this file is ignored.

How to reproduce the problem (as simply and accurately as possible):

Install the azuredisk-csi driver without the resourceManagerEndpoint properties in the azure-cloud-provider secret.

DRIVER_VERSION=v1.10.0
helm repo add azuredisk-csi-driver https://raw.githubusercontent.com/kubernetes-sigs/azuredisk-csi-driver/master/charts
helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver \N- --namespace kube-system``.
  --namespace kube-system \N
  --set cloud=AzureStackCloud \N- --version ${DRIVER} \N- --value
  --version ${DRIVER_VERSION}

Anything else we should know?

But the truth is always in the [source code] (https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/pkg/provider/azure.go#L613) :).So, in the cloud-config file, in the namespace kube-system and the secret azure-cloud-provider, we need to add the properties resourceManagerEndpoint

Environment:

• Kubernetes version (use kubectl version): RKE2 1.27
• Cloud provider or hardware configuration: Azure Stack
• OS (e.g: cat /etc/os-release): Ubuntu 20.04
• Kernel (e.g. uname -a): Ubuntu 20.04

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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-sigs/prow repository.