You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The action should pass successfully and the workflow should start using the K8S context i choose as its Kubernetes context.
Actual Behavior
The actions hangs for few minutes and then fails with the message:
##[error]{"error":{"code":"BadGatewayConnection","message":"The network connectivity issue encountered for 'Microsoft.ContainerService'; cannot fulfill the request."}}
##[error]Node run failed with exit code 1
Steps to Reproduce the Problem
Use aks-set-context action as follows:
# Set the target AKS cluster
- name: Set k8s contextuses: Azure/aks-set-context@v1with:
creds: "${{ env.azure_service_principal }}"resource-group: abcd-qacluster-name: abcd-qa-k8s
Trigger the workflow.
Notes
The same workflow worked just minutes before this issue began to occur - same workflow with exactly the same YAML and exactly the same credentials etc. Nothing was changed neither in the workflow nor the environment!
I tried recreating a service principal using az ad sp create-for-rbac --sdk-auth and changed the workflow to use that, it didn't help.
The text was updated successfully, but these errors were encountered:
Expected Behavior
The action should pass successfully and the workflow should start using the K8S context i choose as its Kubernetes context.
Actual Behavior
The actions hangs for few minutes and then fails with the message:
Steps to Reproduce the Problem
aks-set-context
action as follows:Notes
Nothing was changed neither in the workflow nor the environment!
az ad sp create-for-rbac --sdk-auth
and changed the workflow to use that, it didn't help.The text was updated successfully, but these errors were encountered: