@Halyna Berezovska @Yevhen @Oleksandr Kyrdan I solved this issue .
the solution for this issue is that you have to give the service principal as a contributor role and we have to attach that service principal to the AKS cluster that we using for the deployment
Thanks,
Sanket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for contributing and sharing the solution with the community!
Best regards,
Oleksandr Kyrdan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Reethu are you still having the issue?
Unfortunately, I should announce that microsoft does not support this pipe anymore. Instead atlassian supports this instead. Please, use readme from here for more examples https://bitbucket.org/atlassian/azure-aks-deploy/src/master/ .
If you're still having the issue, could you please share more logs? I've just executed both variants (BIT with space, pipe: atlassian/azure-aks-deploy:1.0.2) and it worked.
Please, report to us, if you have questions or issues with this pipe. For now I cannot reproduce your case.
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Halyna Berezovska @Reethu
I am also facing same issue with
- pipe: microsoft/azure-aks-deploy:1.0.2
following is the error i am getting:
ERROR: The received access token is not valid: at least one of the claims 'puid' or 'altsecid' or 'oid' should be present. If you are accessing as application please make sure service principal is properly created in the tenant.
✖ Error logging in using azure service principal!
+ echo 'ERROR: The received access token is not valid: at least one of the claims '\''puid'\'' or '\''altsecid'\'' or '\''oid'\'' should be present. If you are accessing as application please make sure service principal is properly created in the tenant.'
+ [[ 1 != \0 ]]
+ fail 'Error logging in using azure service principal!'
+ echo -e '\e[31m✖ Error logging in using azure service principal!\e[0m'
+ exit 1
Please help me with this issue. i already wasted 2 days to look into this issue but not getting solution.
@Reethu if you already solve this issue your help would be appriciate.
Regards
Sanket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sanket Sultan the application says to you that your token does not have enough permissions scope
The received access token is not valid: at least one of the claims '\''puid'\'' or '\''altsecid'\'' or '\''oid'\'' should be present.
Recheck your credentials including azure app password, you're passing.
Also, we recommend to switch to
- pipe: atlassian/azure-aks-deploy:1.0.2
I have to remind that microsoft has stoppped maintaining the pipe.
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Reethu ,
Thank you for your question!
It would be nice if you could share with us more details about your case: logs, pipelines configuration, etc.
Cheers,
Oleksandr Kyrdan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Oleksandr for prompt response.
while configuring the bitbucket pipeline to deploy my image from azure container registry to azure kubernetes, i am using two steps:
- Build -(ran successfully)
- step: &Deploy
image:
name: atlassian/default-image:2
name: Deploy Image
trigger: manual
script:
- pipe:microsoft
/azure-aks-deploy:1.0.2
variables:
AZURE_APP_ID: *****
AZURE_PASSWORD: ****
AZURE_TENANT_ID: ******
AZURE_AKS_NAME: ******
AZURE_RESOURCE_GROUP: ******
KUBECTL_COMMAND: 'apply'
KUBECTL_ARGUMENTS: '-f ******.yaml'
DEBUG: 'true' # Optional
while triggering the deploy from pipeline , am getting error like below on executing script in deploy step.+ pipe:microsoft/azure-aks-deploy:1.0.2
bash: pipe:microsoft/azure-aks-deploy:1.0.2: No such file or directory.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.