You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello Bitbucket Community,
I'm currently using the Azure AKS Helm Deploy Pipe in my CI/CD pipeline and have encountered issues related to Azure AD authentication and private cluster support. I'd like to inquire about the maintenance status of this pipe and whether there are plans to add support for these features. If you have insights or know of any alternatives or workarounds, your input would be greatly appreciated.
script: - pipe: atlassian/azure-aks-helm-deploy:3.0.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID AZURE_AKS_NAME: $AZURE_AKS_NAME AZURE_RESOURCE_GROUP: $AZURE_RESOURCE_GROUP HELM_VERSION: 'v3.5.4' HELM_RELEASE_NAME: 'myRedis' HELM_COMMAND: 'upgrade' HELM_UPGRADE_INSTALL_IF_NOT_PRESENT: 'true' HELM_CHART_NAME: 'oci://registry-1.docker.io/bitnamicharts/redis' HELM_COMMAND_ARGS: '--version 18.0.0'
Thank you @Igor Stoyanov for the response.
I'm currently facing an issue when attempting to deploy to a private AKS cluster.
The deployment fails while connecting via kubeconfig, and the error message is as follows:
+ output='Error: Kubernetes cluster unreachable: Get "private link": getting credentials: exec: executable kubelogin not found 2109 2110 It looks like you are trying to use a client-go credential plugin that is not installed. 2111 2112 To learn more about this feature, consult the documentation available at: 2113 2114 2115 2116 kubelogin is not installed which is required to connect to AAD enabled cluster. 2117 2118 To learn more, please go to'
It seems that kubelogin is required to connect to an Azure AD (AAD) enabled cluster, and it's not installed. You can find more information on this feature at this link.
I also attempted to add the bastion server as a known host, but the pipeline doesn't support passing the host to replace the private link with the known host.
I'm unsure if adding code to replace the host should be incorporated into the pipeline.
Your guidance on this matter would be appreciated.
@Avinash Sachdewani, I could suggest just some common things:
First try to deploy from your working machine to understand the process.
After success, try to use pipelines, the script below allows you to use latest azure-cli:
<your logic from previous step, commands you used to deploy from local machine>