Kubectl Gs

  • Changed

    • Make all kubectl config flags (e.g --context and --kubeconfig global and unify kubeconfig management throughout commands.
    • Remove CAPA templating from aws provider.
    • Add new provider capa for templating a cluster.
    • Remove fetching ssh sso ca pub key for capa from management cluster.
    • Add test for CAPA provider cluster templating.
  • Added

    • In the login command, allow concatenation of contexts in destination file when creating WC client certificates with --self-contained flag.
  • Added

    • Allow calling login command with a second argument to select WC contexts.
    • Add -clientcert suffix to WC client certificate contexts created by the login command. Fall back to -clientcert context selection if no other context exists for a cluster.
    • Use CertificateAuthorityData to store CA data and ensure that CertificateAuthority is not set when manipulating the kubeconfig in the login command.
  • Changed

    • Command template cluster --provider gcp no longer tries to get SSH SSO public key secret in the giantswarm namespace
  • Added

    • Add flags --gcp-control-plane-sa-email and --gcp-control-plane-sa-scopes to template cluster that specify a Google Cloud Platform service account and its scopes to a cluster’s control plane nodes

    Removed

    • Removed giantswarm.io/cluster label from the default apps bundle and the App representing a CAPI cluster.
  • Added

    • Added flag --service-priority to template cluster command that allows setting the service priority label.
    • Updated kubectl gs template catalog to support multiple repository mirrors.
  • Removed

    • Remove giantswarm.io/managed-by: flux for App CRs labeled for unique App Operator.
  • Added

    • In the template app command, add the giantswarm.io/cluster label to in-cluster App CR when requested by the user.
  • Added

    • Add service-priority label value highest by default to vintage clusters
    • Add SERVICE PRIORITY column to get clusters command table output.
  • Fixed

    • Take --context flag into account when building config for login.

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.