Add generic control plane staging repository

[carlory]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add generic control plane staging repository
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4080-generic-controlplane
• Discussion Link: KEP-4080: Sig-API-Machinery: Add generic control plane staging repository(ies) #4052
• Primary contact (assignee): @sttts @MikeSpreitzer
• Responsible SIGs: sig-apimachinery,sig-architecture
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):

1.28

• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4080: Sig-API-Machinery: Add generic control plane staging repository(ies) #4052
  • Code (k/k) update PR(s):
    - kube-apiserver/cmd: stratify construction to follow options/config/server pattern kubernetes#118379
    - kube-apiserver: split apart generic control plane options kubernetes#118633
  • Docs (k/website) update PR(s):

1.29

• Alpha
  • [] KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    - controlplane/apiserver: don't crash if authz or other options are explicitly disabled in options kubernetes#120908
    - Step 3 – generic controlplane: split server kubernetes#120202
  • Docs (k/website) update PR(s):

1.31

• Alpha
  • [] KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    - Step 1 – pkg/controlplane: split up config into generic controlplane and kube-related part kubernetes#124551
    - Step 2 – controlplane/apiserver: move peer proxy code to allow generic aggregator construction kubernetes#124576
    - Step 3 – prefactoring: generic controlplane: split out SystemNamespaces kubernetes#124577
    - Step 5 – generic controplane: split aggregator API priorities kubernetes#124613
    - Step 6 – controlplane: cosmetics kubernetes#124620
    - Step 7 – kube-apiserver: split admission initializers into generic and non-generic kubernetes#124621
    - Step 8 – kube-apiserver: split up config creation into generic and non-generic part kubernetes#124638
    - Step 9 – aggregator: move construction to generic controlplane kubernetes#124654
    - Step 10 – controlplane: add generic storage construction kubernetes#124658
    - Step 11 - Split aggregator availability controller into local and remote part kubernetes#126149
    - Step 12 - Add generic controlplane example kubernetes#124530
    - WIP: Step 13 - Add more minimal controlplane example kubernetes#126260
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[carlory]

/sig api-machinery

[carlory]

/sig architecture

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[carlory]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[carlory]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[carlory]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[carlory]

/remove-lifecycle stale