github kubernetes/kops v1.19.0-alpha.2

(The kops 1.19 series has not been released yet; this is a pre-release).

kops 1.19.0-alpha.2 is the next alpha in the 1.19 series for kops.

Please see the release notes for the full list of changes.

Significant changes

Changes to kubernetes config export

Kops will no longer automatically export the kubernetes config on kops update cluster. In order to export the config on cluster update, you need to either add the --user <user> to reference an existing user, or --admin to export the cluster admin user. If neither flag is passed, the kubernetes config will not be modified. This makes it easier to reuse user definitions across clusters should you, for example, use OIDC for authentication.

Similarly, kops export kubecfg will also require passing either the --admin or --user flag if the context does not already exist.

kops create cluster --yes exports the admin user along with rest of the cluster config, as is existing behaviour.

Other significant changes

  • New clusters will now have one nodes group per zone. The number of nodes now defaults to the number of zones.

  • On AWS kops now defaults to using launch templates instead of launch configurations.

  • Clusters using the Amazon VPC CNI provider now perform an ec2.DescribeInstanceTypes call at instance launch time. In large clusters or AWS accounts this may lead to API throttling which could delay node readiness. If this becomes a problem please open a GitHub issue.

  • Alpha support for Hashicorp Vault as store for secrets and keys. See the Vault state store docs.

  • New clusters running Cilium will have enabled BPF NodePort by default if kubernetes version is 1.12 or newer.

  • The kops update cluster command will now refuse to run on a cluster that
    has been updated by a newer version of kops unless it is given the --allow-kops-downgrade flag.

Breaking changes

  • Support for Kubernetes 1.9 and 1.10 has been removed.

  • Support for the Romana networking provider has been removed.

  • Support for legacy IAM permissions has been removed. This removal may be temporarily deferred to kops 1.20 by setting the LegacyIAM feature flag.

Required Actions


  • Support for Kubernetes versions 1.11 and 1.12 are deprecated and will be removed in kops 1.20.

Change list

Changes from 1.19.0-alpha.1 to 1.19.0-alpha.2

Please see the release notes for the full list of changes.

latest releases: v1.19.0-beta.2, v1.19.0-beta.1, v1.18.2...
pre-release3 months ago