gsctl

  • New features

    • Added a new --releases flag to the upgrade cluster command to specify which release to upgrade the cluster to.
  • New features

    • Display information about Kubernetes versions that are no longer supported, or versions that will become unsupported soon (#594)

    Minor changes

    • Don’t encourage the usage of pre-release versions (#596)
  • Minor changes

    • Change example Azure node pool VM Size. (#593)
    • Temporarily remove support for Azure node pool autoscaling. (#595)
  • Minor changes

    • Validate if node pool is actually changed before sending the update API request. (#590)
  • New features

    • Added global --silence-http-endpoint-warning which allows silencing warnings emitted when using an non https endpoint url (#582)

    Other changes

    • Updated internals to use Kubernetes 1.18 libs (#584)
    • gsctl is now compiled using go version 1.15.2 (#586)
    • Fixed a typo in create kubeconfig flag description (#585)
  • New features

    • Added JSON formatted output via --output flag to gsctl create cluster, gsctl create kubeconfig and gsctl delete cluster to make automation use cases easier
    • It is now possible to specify the release version with a v in gsctl create cluster
    • Allow m5.8xlarge, m5.12xlarge, m5.16xlarge, m5.24xlarge, r5.xlarge, r5.4xlarge, r5.8xlarge and r5.12xlarge instance types in cluster creation on AWS

    Fixes

    • Fixed an issue which made it difficult to create clusters with --endpoint and --auth-token flags
    • gsctl list clusters now returns [] instead of null when called with --output json for empty cluster lists
    • gsctl list releases no longer omits the active attribute for non-active releases when called with --output json
  • New features

    • Add support for new node pool attributes related to spot instances and using alike instance types
  • New features

    • This gsctl release adds support for high availability Kubernetes masters which is available on AWS starting with release v11.4.0 (#554, #561). The changes in detail are:
      • gsctl create cluster now supports specifying multiple/single master nodes. Note: on AWS from v11.4.0, clusters will have multiple master nodes by default.
      • gsctl update cluster allows converting a single master cluster on AWS with release v11.4.0 and higher to a multi master cluster. Check the details for the --master-ha flag in the reference.
      • The gsctl show cluster command shows details on master nodes, including the number of nodes in Ready state and their availability zones.
    • We added support for the Fish shell to the gsctl completion command. Add --help for instructions. (#558, #559)

    Fixes

    • Panic in gsctl list nodepools due to slice bounds out of range (#563)
  • We added a link to our security policy. Please visit https://www.giantswarm.io/responsible-disclosure for information on reporting security issues.

    Minor changes

    • The info command now displays all the possible environmental variables. (#555)
    • The cluster labels now use the same placeholder as other fields. (#556)

    Bugfixes

    • The scale cluster command --num-workers flag was no longer working after an update on the command flags. (#557)
  • New features

    • We introduce a new --sort/-s flag to the gsctl list clusters command to allow you to influence the output ordering. Sorting your tons of clusters by release, owner organization or creation date? Here you go.

    Minor changes

    • To get the version of gsctl, please use gsctl --version from now on. The old command gsctl version will show you a deprecation warning and will be removed at some point in the future.