Skip to content

Workload API #353

@kow3ns

Description

@kow3ns

Feature Description

  • One-line feature description (can be used as a release note): The core workload API (DaemonSet, Deployment, ReplicaSet, StatefulSet) have been moved to the apps group at version v1beta2.
  • Primary contact (assignee): @kow3ns
  • Responsible SIGs: apps
  • Design proposal link (community repo): NA
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @Kargakis @janetkuo @foxish @enisoc @crimsonfaith91
  • Approver (likely from SIG/area to which feature belongs): @smarterclayton @erictune
  • Feature branch : https://github.com/kubernetes/kubernetes/tree/feature-workload-ga
  • Feature target (which target equals to which milestone):
    • Beta release target (1.8)
    • GA release target (1.9)

Create a new version in the apps group for the core workloads API.
When we advance the core workloads API (DaemonSet, Deployment, ReplicaSet, and StatefulSet) to v1, we want them to advance as a group and be (where possible) consistent. Prior to doing so, we would like to make any API incompatible changes. In particular we will

  • move DaemonSet to apps
  • remove the TemplateGeneration field of DaemonSet
  • change the StatefulSet ObservedGeneration from a pointer to an int for consistency.
  • remove the /rollback subresource of Deployment, or modify it such that the controller is not required to modify its own spec.
  • add a scale subresource for StatefulSet
  • review the API objects for consistency, and (where appropriate) make changes to bring them into alignment (modifying field names a necessary).
  • ensure that the defaults and validation are consistent and appropriate across all controllers.

We may find other incompatible changes that are required prior to promotion, and we would like to make them in this version, prior to releasing it. When the community is satisfied with the API surface, as contained in this version, and it is stable, we would like to promote all of the core workloads API to GA by moving the contained API to v1.

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.sig/appsCategorizes an issue or PR as relevant to SIG Apps.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA status

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions