Skip to content

Latest commit

 

History

History
99 lines (67 loc) · 3.11 KB

ROADMAP.md

File metadata and controls

99 lines (67 loc) · 3.11 KB
Raw

ROADMAP

The kops 1.N.x version officially supports kubernetes 1.N.x and earlier. While kubernetes 1.99 will likely run with kops 1.98, the configuration will probably not be correct (for example docker versions, CNI versions etc).

kops 1.N.0 is released when it is believed that kubernetes 1.N.x is stable, along with all the core addons (e.g. networking). This can mean that kops can release months after the release of kubernetes. It's also not a deterministic release criteria, particularly with some networking plugins that are supported by kops but themselves still under development. We discussed this challenge in kops office hours in March 2018, and the consensus was that we want to keep this, but that we should release alphas & betas much earlier so that users can try out new kubernetes versions on release day.

For the next few releases this means that:

  • 1.9.0 release target April 7th
  • 1.10 alpha.1 with release of kops 1.9.0 (April 7th)
  • 1.10 release target April 28th
  • 1.11 alpha.1 at release of kops 1.10
  • 1.11 beta.1 at release of k8s 1.11
  • 1.12 alpha.1 at release of kops 1.11 etc

kops 1.10

  • Support for kubernetes 1.10
  • Full support for GCE
  • Make the etcd-backup tool enabled-by-default, so everyone should have backups.
  • Allow users to opt-in to the full etcd-manager.
  • Make etcd3 the default for new clusters, now that we have an upgrade path.
  • Beginning of separation of addon functionality
  • Support for more clouds (Aliyun, DigitalOcean, OpenStack)

kops 1.11

  • Make the etcd-manager the default, deprecate the protokube-integrated approach
  • kops-server
  • Machines API support (including bare-metal)

HISTORICAL

1.9

Must-have features

  • Support for k8s 1.9 done
  • etcd backup support done

Other features

  • Use NodeAuthorizer / bootstrap kubeconfigs #3551 no progress; may be less important with machines API

1.8

Must-have features

  • Support for k8s 1.8

Other features

  • Improved GCE support
  • Support for API aggregation

1.7

Must-have features

  • Support for k8s 1.7

Other features we are working on in the 1.7 timeframe

  • etcd controller to allow moving between versions
  • kops server for better team scenarios
  • support for bare-metal
  • more gossip backends
  • IAM integration
  • more cloud providers
  • promote GCE to stable
  • RBAC policies for all components
  • bringing rolling-update out of alpha

1.6

Must-have features

  • Support for k8s 1.6 done
  • RBAC enabled by default yes, but we kept RBAC optional

Other features we are working on in the 1.6 timeframe

  • Support for GCE alpha
  • Support for Google's Container Optimized OS (formerly known as GCI) alpha
  • Some support for bare-metal private branches, not merged
  • Some support for more cloud providers initial work on vsphere
  • Some IAM integration discussions, but no code
  • Federation made easy no progress
  • Authentication made easy no progress
  • Integration with kubeadm kops now uses kubeadm for some RBAC related functionality
  • CloudFormation integration on AWS beta