Skip to content

Pod self-orchestration #5309

Open
Open
@SergeyKanzhelev

Description

@SergeyKanzhelev

Enhancement Description

  • One-line enhancement description (can be used as a release note):

    Allow to specify one of the containers in a Pod to become an orchestration container. It will receive information about other containers and will be able to influence other containers and the whole Pod lifecycle.

  • Kubernetes Enhancement Proposal: TBD

  • Discussion Link: https://docs.google.com/document/d/1OIpLhfYedbWwSw3wlAlTctrDfW-aYxsjPJNMu-AqFbI/edit?tab=t.0#heading=h.ktam0fckicni

  • Primary contact (assignee): @SergeyKanzhelev

  • Responsible SIGs: node

  • Enhancement target (which target equals to which milestone):

    • Alpha release target (x.y): 1.34
    • Beta release target (x.y):
    • Stable release target (x.y):
  • Alpha

    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):

/sig node

Metadata

Metadata

Assignees

No one assigned

    Labels

    sig/nodeCategorizes an issue or PR as relevant to SIG Node.

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions