Skip to content

RFC: Support user defined and extensible deployment strategies #14510

Open
@ironcladlou

Description

The new deployment API (#1743) specifies some out of the box strategies (recreate, rolling) which will be implemented inside the deployment controller. It's possible these strategies may not cover all deployment needs for end users, or for downstream users (such as OpenShift). The deployment system should enable:

  1. Users to define their own deployment strategy logic in a custom Docker image.
  2. Downstream systems to define deployment strategies in a delegate controller.

It's possible these two capabilities are related but orthogonal in their design/implementation. I'm starting the discussion here so we can collect initial thoughts and start linking any existing relevant issues.

Metadata

Assignees

Labels

area/app-lifecyclearea/workload-api/deploymentkind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.sig/appsCategorizes an issue or PR as relevant to SIG Apps.

Type

No type

Projects

  • Status

    Needs Triage

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions