Skip to content

Releases: Azure/kubectl-aks

v0.2.4

08 Feb 21:33
34574f2
Compare
Choose a tag to compare

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 @mqasimsarfraz for this contribution and to @vmarcella and @mbifeld for the support in this task.

What's Changed

  • build(deps): bump golang.org/x/net from 0.7.0 to 0.17.0 by @dependabot in #49
  • ci: Allow running tests in parallel by @mqasimsarfraz in #50
  • docs: Add documentation-test for README by @mqasimsarfraz in #51
  • build(deps): bump golang.org/x/crypto from 0.14.0 to 0.17.0 by @dependabot in #53
  • docs: Improve check-apiserver-connectivity description by @blanquicet in #54
  • config: Use data from config file when available by @blanquicet in #55
  • spinner: Ensure there are no logs/prints between Start and Stop by @blanquicet in #61

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

v0.2.3

02 Oct 08:25
f8ef83e
Compare
Choose a tag to compare

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

  • docs: Update run-command documentation to use the config command by @blanquicet in #45
  • ci: Use federated credential to login to Azure by @mqasimsarfraz in #46
  • Added darwin arm64 krew by @kim-sondrup in #47
  • azure: Upgrade dependencies for armcontainerservice by @mqasimsarfraz in #48

New Contributors

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

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

v0.2.2

27 Jul 14:24
2b131fa
Compare
Choose a tag to compare

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

30 May 10:33
cf44911
Compare
Choose a tag to compare

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

  • readme: Add krew installation instructions and improve description by @blanquicet in #27
  • run-command: Introduce timeout for run-command by @mqasimsarfraz in #34
  • run-command: Truncate output tail instead of head by default by @blanquicet in #36

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

v0.2.0

26 Apr 10:37
c3956ef
Compare
Choose a tag to compare

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

05 Apr 17:50
f73caa5
Compare
Choose a tag to compare

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