az aks get-credentials crashed - API version 2022-04-01 does not have operation group 'managed_clusters'
See original GitHub issueThis is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks get-credentials
Errors:
The command failed with an unexpected error. Here is the traceback:
API version 2022-04-01 does not have operation group 'managed_clusters'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/knack/cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 663, in execute
raise ex
File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
result = cmd_copy(params)
File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
return self.handler(*args, **kwargs)
File "/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", line 112, in handler
client = self.client_factory(self.cli_ctx, command_args) if self.client_factory else None
File "/usr/lib/python3/dist-packages/azure/cli/command_modules/acs/_client_factory.py", line 22, in cf_managed_clusters
return get_container_service_client(cli_ctx).managed_clusters
File "/usr/lib/python3/dist-packages/azure/mgmt/containerservice/_container_service_client.py", line 492, in managed_clusters
raise ValueError("API version {} does not have operation group 'managed_clusters'".format(api_version))
ValueError: API version 2022-04-01 does not have operation group 'managed_clusters'
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- Put any pre-requisite steps here…
az aks get-credentials --resource-group {} --name {}
Expected Behavior
Environment Summary
Linux-5.18.0-kali5-amd64-x86_64-with-glibc2.33, Kali GNU/Linux Rolling
Python 3.10.5
Installer: DEB
azure-cli 2.38.0
Extensions:
azure-devops 0.24.0
Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.0.0
Additional Context
Installed from repo: deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ bullseye main
Older version of az-cli like 2.28 works.
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Troubleshoot Azure Kubernetes Service cluster creation issues
Learn about basic troubleshooting methods to use when you can't create or deploy an Azure Kubernetes Service (AKS) cluster.
Read more >Azure Kubernetes Error when running "az aks get-credentials ...
I am getting error: ForbiddenError: The client 'my_name@my_comp.COM' with object id '4ea46ad637c6' does not have authorization to perform action ...
Read more >Securing Azure Kubernetes and workloads - Marius Sandbu
NOTE: You can still get access to the admin using the cluster credentials by using the command az aks get-credentials –resource-group ...
Read more >Get to Grips with Azure AD and AKS - samcogan.com
Microsoft has done a lot of work to integrate their Azure Kubernetes Service (AKS) with Azure Active Directory. However, there have been ...
Read more >Aks Minimum Permissions - Steve Griffith
Azure will provide these to you using the az aks get-credentials ... level or above (i.e. Cluster, Resource Group or Subscription) az role ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For 2.37 works and olders. The problem is with 2.38 version 😦
Hi, we’re sending this friendly reminder because we haven’t heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don’t hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!