Kubectl Gs

  • Changed

    • Use Phase instead of Status field for Clusters and Nodepools. Affected commands:
      • kubectl gs get clusters
      • kubectl gs get nodepools

    Fixed

    • Fix getting nodepools via kubectl gs get nodepools.
    • Remove node classes from vsphere template used in kubectl gs template cluster command.
  • Changed

    • Adjust columns for kubectl gs get releases.
  • Added

    • Cloud Director Provider.
  • Fixed

    • Fixed unique user tracking
    • Remove debug logging regarding telemetry
  • Added

    • Basic usage tracking data is now collected for every command execution. This should help us maintain and develop the tool. Set the KUBECTL_GS_TELEMETRY_OPTOUT environment variable to an arbitrary value to disable this. Data is submitted to TelemetryDeck in the EU. More details are available in our docs.
  • Changed

    • BREAKING When templating cluster manifests for CAPV clusters with kubectl gs template cluster command, now we set the workload cluster release version via the --release flag, instead setting cluster-vsphere version via --cluster-version.
  • Added

    • Add support for unified cluster-vsphere app. With cluster-vsphere v0.61.0 and newer, default apps are deployed with cluster-vsphere, and default-apps-vsphere app is not deployed anymore.
  • Changed

    • The way to specify a release in kubectl gs gitops add workload-cluster has changed. The flag --cluster-release has been replaced by --release.

    Removed

    • kubectl gs gitops add workload-cluster:
      • The flag --default-apps-user-config has been removed
      • The flag --default-apps-release has been removed
      • The flag --cluster-release has been removed
  • Changed

    • Use more portable, Bash specific shebang for GitOps pre-commit script template
    • Schedule cluster upgrades for CAPI clusters.
    • Print Release information in get cluster command.
  • Added

    • Add --prevent-deletion flag to cluster template command for capv clusters
    • Helpful error messages for invalid subnet split parameters of CAPA private clusters

    Changed

    • BREAKING When templating cluster manifests for CAPZ clusters with kubectl gs template cluster command, now we set the workload cluster release version via the --release flag, instead setting cluster-azure version via --cluster-version.

This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.