Skip to content

Releases: Azure/kubectl-aks

Release v0.3.0

Choose a tag to compare

@github-actions github-actions released this 20 May 10:20
f0a5f2e

This release includes many new features for effective AKS cluster troubleshooting especially when API server is down:

Cluster-wide checks

You can now run checks across the entire cluster, making it easier to identify issues affecting multiple nodes or workloads during outages and degraded cluster states.

→ kubectl aks check verify apiserver-connectivity
✔ (all nodes in cluster)
=== aks-nodepool1-58771399-vmss000008 ===
✓ Connectivity check: succeeded

=== aks-nodepool1-58771399-vmss000009 ===
✓ Connectivity check: succeeded

=== aks-nodepool1-58771399-vmss000007 ===
✓ Connectivity check: succeeded

Generic troubleshooting checks

Added a new framework for generic checks to simplify diagnostics and provide reusable validation logic across different troubleshooting scenarios with checks powered by Inspektor Gadget.

→ kubectl aks check trace dns-failed
✔ (all nodes in cluster)
=== aks-nodepool1-58771399-vmss000008 ===
✓ DNS trace: no DNS failures observed during trace period

=== aks-nodepool1-58771399-vmss000009 ===
✗ DNS trace: 3 DNS failure(s) observed
NAME                                                                                                             RCODE      QTYPE  NAMESERVER    POD                                       PROCESS
ama-metrics-operator-targets.kube-system.svc.cluster.local.porvznvo3j2ulmh44ss01jatoe.fx.internal.cloudapp.net.  NameError  A      10.244.0.192                                            
ama-metrics-operator-targets.kube-system.svc.cluster.local.porvznvo3j2ulmh44ss01jatoe.fx.internal.cloudapp.net.  NameError  A      10.0.0.10                                               systemd-resolve(657)
ama-metrics-operator-targets.kube-system.svc.cluster.local.porvznvo3j2ulmh44ss01jatoe.fx.internal.cloudapp.net.  NameError  A      10.0.0.10     kube-system/ama-metrics-5f7f4b8b7d-47tjn  flb-pipeline(1476927)


=== aks-nodepool1-58771399-vmss000007 ===
✓ DNS trace: no DNS failures observed during trace period

You can see documentation on writing a check and sharing it with the entire community.

What's Changed

Full Changelog: v0.2.5...v0.3.0

Release v0.2.5

Choose a tag to compare

@github-actions github-actions released this 12 May 14:51
22a7155

This release includes new features, bug fixes, and dependency updates.

The important changes are support for different Azure clouds (AzureUSGovernment/AzureChina) and a new kube-api runtime. Additionally, a security fix upgrades logrus to address CVE-2025-65637.

What's Changed

Full Changelog: v0.2.4...v0.2.5

v0.2.4

Choose a tag to compare

@github-actions github-actions released this 08 Feb 21:33
34574f2

This is a release with few changes from the user perspective as it mostly includes some improvements in the documentation and CI.

The most important change is that we are now using the InnovationEngine to validate the code blocks present in the README file. This will help us to ensure that the documentation is always up to date and that the code blocks are working as expected. The same strategy will be applied to the rest of the documentation in the future. Thanks to Qasim Sarfraz (@mqasimsarfraz) for this contribution and to Vincenzo Marcella (@vmarcella) and Mitchell Bifeld (@mbifeld) for the support in this task.

What's Changed

Full Changelog: v0.2.3...v0.2.4

v0.2.3

Choose a tag to compare

@mqasimsarfraz mqasimsarfraz released this 02 Oct 08:25
f8ef83e

This is a bug fix release and allows installing kubectl aks (via krew) on darwin arm64, thanks to @kim-sondrup. It also upgrade azure sdk to use newer API versions alongside documentation updates.

What's Changed

New Contributors

  • @kim-sondrup made their first contribution in #47

Full Changelog: v0.2.2...v0.2.3

v0.2.2

Choose a tag to compare

@github-actions github-actions released this 27 Jul 14:24
2b131fa

In this release, we bring you more UX improvements with signal handling, redirection of stdout/stderr and spinner while using run-command. Also, config import now supports importing node information using Azure API, making it easier to use kubectl-aks even if you don't have access to the Kubernetes API server.

What's Changed

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Choose a tag to compare

@mqasimsarfraz mqasimsarfraz released this 30 May 10:33
cf44911

In this release we are bringing in couple of UX improvements with run-command now having a default timeout of 300 seconds compared to 90 mins and improving the output of run-command by truncating the tail instead of head by default. For details please refer to changes below:

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Choose a tag to compare

@mqasimsarfraz mqasimsarfraz released this 26 Apr 10:37
c3956ef

In this release we renamed the project from kubectl-az to kubectl-aks to make the usage clearer. Feedback and suggestions are always welcome.

What's Changed

Full Changelog: v0.1.0...v0.2.0

Features

The following commands are available in this version:

  • run-command: run a command in a node
  • check-apiserver-connectivity: check connectivity between the nodes and the Kubernetes API Server
  • config: manage configuration

Installation

You can install kubectl-aks by downloading the asset for a given release and platform from the releases page on GitHub. Alternatively, you can build kubectl-aks from source by cloning the repository and running the make install command.

Usage

To use this plugin, run the kubectl aks command followed by the desired subcommand. The available subcommands are check-apiserver-connectivity, completion, config, help, run-command, and version.

Note that it is necessary to sign in to Azure to run most of kubectl-aks commands. You can use any authentication method provided by the Azure CLI using the az login command. If you have not signed in yet, kubectl-aks will open the default browser and load the Azure sign-in page where you need to authenticate.

Please refer to the documentation for each command to understand how to use them and which one is the most suitable for your case.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 05 Apr 17:50
f73caa5

The first version of the kubectl-az plugin is now available, providing a set of commands to debug an AKS cluster even when the control plane is not working correctly. With this release, users can complement their az CLI experience with additional commands and have a kubectl-like experience when working with an AKS cluster.

Features

The following commands are available in this version:

  • run-command: run a command in a node
  • check-apiserver-connectivity: check connectivity between the nodes and the Kubernetes API Server
  • config: manage configuration

Installation

You can install kubectl-az by downloading the asset for a given release and platform from the releases page on GitHub. Alternatively, you can build kubectl-az from source by cloning the repository and running the make install command.

Usage

To use this plugin, run the kubectl az command followed by the desired subcommand. The available subcommands are check-apiserver-connectivity, completion, config, help, run-command, and version.

Note that it is necessary to sign in to Azure to run most of kubectl-az commands. You can use any authentication method provided by the Azure CLI using the az login command. If you have not signed in yet, kubectl-az will open the default browser and load the Azure sign-in page where you need to authenticate.

Please refer to the documentation for each command to understand how to use them and which one is the most suitable for your case.

New Contributors

Full Changelog: https://github.com/Azure/kubectl-az/commits/v0.1.0