kops icon indicating copy to clipboard operation
kops copied to clipboard
verified publisher icon kubernetes

Create criteria for cloud providers to graduate to beta or GA

Open johngmyers opened this issue 4 years ago • 6 comments

Decide and document criteria for a cloud provider to graduate to beta or GA status.

Things to consider:

  • e2e tests
  • e2e presubmit
  • kops toolbox instance-selector
  • UseKopsControllerForNodeBootstrap
  • dns-controller
  • apiserver node role
  • instancegroup volumes
  • serviceaccount IAM
  • encryptEtcdStorage by default for new clusters
  • private topology
  • terraform target
  • rolling-update surge
  • non-legacy nodeidentity.Identifier (node labels from cloud tags)
  • default NTP host

Things that are likely AWS specific, so out of scope:

  • warm pools
  • Vault for secretstore and keystore
  • Cilium ENI IPAM
  • Node Termination Handler
  • IPv6
  • ARM instances
  • instance group tenancy
  • external-dns (it's still feature flagged)

johngmyers avatar May 30 '21 22:05 johngmyers

Feature-wise I think these are good points.

I also think we need some criterias around

  • active maintainers
  • access to dev environments

olemarkus avatar May 31 '21 09:05 olemarkus

I doubt a cloud provider would meet whatever feature parity requirement we set without an active maintainer.

Does AWS even meet an "access to dev environments" requirement? My access to an AWS dev environment is through my employer, without which I would have to give AWS my credit card and risk four-figure bills due to AWS's lack of spending limits.

johngmyers avatar May 31 '21 15:05 johngmyers

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Aug 29 '21 15:08 k8s-triage-robot

/remove-lifecycle stale

hakman avatar Aug 29 '21 17:08 hakman

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Nov 27 '21 18:11 k8s-triage-robot

/remove-lifecycle stale /lifecycle frozen

johngmyers avatar Nov 27 '21 22:11 johngmyers