Minor changes
The list releases command will now print a deprecation message to STDERR.
gsctl
-
-
Minor changes
Added note to README about deprecation of
gsctl.All commands which have a direct replacement in
kubectl gsavailable will now print a deprecation warning to STDERR. -
New features
- The configuration path can now be set using the
GSCTL_CONFIG_DIRenvironment variable. Thanks to @kampka for the contribution!
- The configuration path can now be set using the
-
A new major release? Well, for no special reason. We wanted to get rid of the leading zero for quite some time.
New features
- The
gsctl create kubeconfigcommand now offers the--kubieflag. When kubie is installed and the flag is used, a new shell is launched with the cluster and new key pair as selected kubectl context, without modifying thecurrent-contextin the kubectl config.
Changes
- Use more specific terminology for
releasein help texts:workload cluster release. - Update documentation URLs.
- The
-
New features
- Support for node pool spot instances on Azure, starting with release
v14.1.0.
- Support for node pool spot instances on Azure, starting with release
-
New features
- Allow node pool autoscaling on Azure. (https://github.com/giantswarm/gsctl/pull/602)
- Add the new
--internal-apiflag for thecreate kubeconfigcommand, which will add the new entry to your local kubectl config. (https://github.com/giantswarm/gsctl/pull/604/files)
Bugfixes
- Fix node pool creation on installations that don’t support availability zones (e.g.
germanywestcentralon Azure) (https://github.com/giantswarm/gsctl/pull/603)
-
New features
- Allow having no Master Availability Zone on Azure nodepools clusters. (https://github.com/giantswarm/gsctl/pull/601)
- Allow scaling nodepools to 0 nodes. (https://github.com/giantswarm/gsctl/pull/599)
-
New features
- Added a new
--releasesflag to theupgrade clustercommand to specify which release to upgrade the cluster to.
- Added a new
