Azure / Azure/azure-dev

[Issue] Still Unable to deploy to AKS cluster with Microsoft Entra ID authentication and Azure RBAC enabled

Open
#5,181 0 comments 0 reactions 0 assignees View on GitHub
area/aks bug customer-reported needs-team-attention
Dominant language
Go
Stars
569
Forks
364
Avg merge
2d 19h
Merged PRs (30d)
136

Description

- [x] Make sure you've installed the latest version using [instructions in the wiki](../wiki/install)

**Output from `azd version`**
```
azd version 1.15.1 (commit b8385e796d2a4b2e5b431ddf3fcc2069034d7ce3)
```

**Describe the bug**

Original issue is #5074 . This has been addressed in the PR #5102 , but the same issue persists.

```
Deploying services (azd deploy)

(x) Failed: Deploying service sample

ERROR: failed deploying service 'sample': helm deployment failed: failed to install helm chart sample/sample: exit code: 1, stdout: , stderr: Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials
```

**To Reproduce**
The reproduction steps are the same as for issue #5074 . There is no issue when applying the manifest, but the problem occurs when using Helm. Additionally, it occurs when AZURE_TENANT_ID is not set in the environment variables or the .env file.

This issue appears to have been discussed in PR #5012 , but it seems it was merged as no problem.

**Expected behavior**
azd should be able to login to the cluster and deploy the app

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.