add draft workloads api content for 1.8 #5650

Bradamant3 · 2017-09-27T05:39:22Z

This draft is a dump of the content from the gdoc from sig-apps, very minimally edited and incomplete because the last sections contain tables :-(. Would like to get into core docs even in rough form so that we can link from the release notes, and fix up asap. I can work on it on Wednesday 9/27 probably before and definitely after the release.
Please review only lightly for minimum acceptability, or just toss it back. Here's what I plan still to do:

Edit throughout for clarity, grammar, and punctuation (spelling seems ok on first pass)
Provide a clearer explanation up front of why we're providing this new kind of doc content
Add tables for planned release details

I'll also add Ken as a reviewer after I clean it up some more. He's listed as an approver in the file now, although I'm not sure what effect that listing has.

Also please lmk if you think it's OK to link to the URL from the release notes even if we're not sure the topic will go live before the release notes (in other words, the link may 404 for a day or two).
@steveperry-53 I assigned to you because I figured it was better that folks who know what's going on look at it at this point. If this isn't appropriate, please fix as needed.

This change is

k8sio-netlify-preview-bot · 2017-09-27T05:41:22Z

Deploy preview ready!

Built with commit dc90d57

https://deploy-preview-5650--kubernetes-io-vnext-staging.netlify.com

steveperry-53 · 2017-09-27T15:58:38Z

docs/reference/workloads-18-19.md

+- In the 1.8 release, we introduce the apps/v1beta2 API group and version. This beta version of the core workload API contains the current version of Deployment, DaemonSet,  ReplicaSet, and  StatefulSet, and it is the version we plan to promote, provided the feedback is positive, to GA in the 1.9 release.
+
+- In the 1.9 release, we plan to introduce the apps/v1 API. We intend to promote the you also mentioned that we might want to not mark everything in types.go with +DEPRECATED should we clean this up prior to approval or apps/v1beta2 group version in its entirety to apps/v1 and to deprecate apps/v1beta2 at that time.
+


It looks like a comment got blended into the text here. My guess is this should say, "We intend to promote the apps/v1beta2 group version in its entirety to ..."

steveperry-53 · 2017-09-27T16:05:55Z

docs/reference/workloads-18-19.md

+#### Immutable Selectors
+
+Selector mutation, while allowing for some use cases like promotable Deployment canaries, the core workloads controller do not, in the general case, handle selector mutation gracefully, and we have always strongly cautioned users against it.
+


This sentence has an odd structure, and I truly don't understand it. Who/what doesn't handle selector mutation gracefully? Maybe this: We have always cautioned uses against selector mutation. The core workloads controller does not, in the general case, handle selector mutation gracefully.

steveperry-53 · 2017-09-27T16:06:35Z

docs/reference/workloads-18-19.md

+We believe that there are better ways to support features like promotable canaries and orchestrated Pod relabeling, but, if restricted selector mutation is a necessary feature for our users, we can relax immutability prior to GA without breaking backward compatibility.
+
+The development of features like promotable canaries, orchestrated Pod relabeling,and restricted selector mutability is driven by demand signals from our users. If you are currently modifying the selectors of your core workload API objects, please tell us about your use case in a GitHub issue, or by participating in SIG-apps.
+


relabeling,and -> relabeling, and

but, if -> but if
issue, or -> issue or

steveperry-53 · 2017-09-27T16:06:56Z

@Bradamant3 A few comments. Otherwise lgtm.

steveperry-53 · 2017-09-27T16:11:19Z

@Bradamant3 Let's not put a broken link in the release notes. But let's watch closely, and put the link in as soon as this topic is live.

zacharysarah

Nitpicky editor stuff.

I'm not sure that "kinds" is 100% synonymous with "objects", but given the content discussed (especially StatefulSet, which the docs refer to as an API object; see below) it seems like a better choice.

StatefulSet docs: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets

UPDATE: After talking with @Bradamant3 and looking at K8s objects, "kinds" appears correct. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/

zacharysarah · 2017-09-27T19:55:40Z

docs/reference/workloads-18-19.md

@@ -0,0 +1,57 @@
+---
+title: Workloads API changes in version 1.8 and 1.9


zacharysarah · 2017-09-27T19:57:56Z

docs/reference/workloads-18-19.md

+
+## Overview
+
+The Kubernetes core workload API consists of the Deployment, DaemonSet, ReplicaSet, and StatefulSet API objects. In order to provide a stable API for users to orchestrate their workloads, we are prioritizing promoting the core workload API to GA. The batch workload API (Job and CronJob), while also important, is not part of this effort, and it will have a separate path to GA stability.


I've seen this feature inconsistently capitalized and pluralized. (Core Workloads API, the Workloads API, core workload API, etc.) It would be awesome to determine which combination is authoritative and apply it consistently across the site.

Workloads API is the larger concept per the reference docs. I recommend "Workloads API" but then further modified because:
In v1.7, it includes three groups: extensions, apps, and batch. In 1.8, it includes two groups: apps and batch. The groups also rejoice in different versions. "core" here = extensions + apps, or apps, depending on the version. I don't know what to do about it, but I'm leaving "core" for now bc it helps distinguish between groups. IF you're already something of a K8s API insider, I know. But really this is an API design issue, not a docs issue, so while I agree that we need an authoritative convention, I guess I'm recommending here that we iterate toward said convention.

zacharysarah · 2017-09-27T19:58:50Z

docs/reference/workloads-18-19.md

+
+- If you are using kinds from the extensions/v1beta1 or apps/v1beta1 group versions, you can wait to migrate existing code until after the release of the apps/v1 group version.
+
+- If there are features in the apps/v1beta2 group version that you want to consume, you may migrate to this group version prior to the apps/v1 release.


Maybe "implement" instead of "consume"?

Consume is correct here, not implement.

Could we write around altogether? (I find "consume" unfortunate here -- it's an overloaded term in software already, and this seems like yet another overloading.)
"If your deployment requires features that are available in the apps/v1beta2 group version, you can migrate to this group version before the apps/v1 release."

That's fair, "consumption" for APIs is correct.

zacharysarah · 2017-09-27T19:59:06Z

docs/reference/workloads-18-19.md

+
+- If there are features in the apps/v1beta2 group version that you want to consume, you may migrate to this group version prior to the apps/v1 release.
+
+- You should develop all new code againsts the latest stable release.


againsts -> against

zacharysarah · 2017-09-27T20:00:51Z

docs/reference/workloads-18-19.md

+
+### Migrating to apps/v1beta2
+
+This section provides information on migrating to the apps/v1beta2 group version. It covers general changes to the core workloads API kinds. For changes that affect a specific kind (e.g. defaults), you should consult the reference documentation for the kind.


"It covers general changes to core workloads API objects. For changes that affect a specific object (for example, default values), see the reference documentation for the object."

zacharysarah · 2017-09-27T20:04:07Z

docs/reference/workloads-18-19.md

+
+User feedback led us to determine that, as it is incompatible with strategic merge patch and kubectl apply, defaulting the value of a field from the value of another field of the same object is an anti-pattern.
+
+#### Immutable Selectors


Selectors -> selectors

zacharysarah · 2017-09-27T20:04:29Z

docs/reference/workloads-18-19.md

+
+Selector mutation, while allowing for some use cases like promotable Deployment canaries, the core workloads controller do not, in the general case, handle selector mutation gracefully, and we have always strongly cautioned users against it.
+
+To provide a consistent, usable, and stable API, selectors have been made immutable for all kinds in the apps/v1beta2 group and version.


for all objects

zacharysarah · 2017-09-27T20:05:01Z

docs/reference/workloads-18-19.md

+
+The development of features like promotable canaries, orchestrated Pod relabeling,and restricted selector mutability is driven by demand signals from our users. If you are currently modifying the selectors of your core workload API objects, please tell us about your use case in a GitHub issue, or by participating in SIG-apps.
+
+#### Default Rolling Updates


Rolling Updates -> rolling updates

zacharysarah · 2017-09-27T20:05:16Z

docs/reference/workloads-18-19.md

+
+#### Default Rolling Updates
+
+Prior to apps/v1beta2, some kinds defaulted the spec.updateStrategy to a strategy other than RollingUpdate. For example, app/v1beta1 StatefulSet specifies OnDelete by default. In apps/v1beta2 the spec.updateStrategy for all kinds defaults to RollingUpdate.


some kinds -> some objects

zacharysarah · 2017-09-27T20:05:32Z

docs/reference/workloads-18-19.md

+
+Prior to apps/v1beta2, some kinds defaulted the spec.updateStrategy to a strategy other than RollingUpdate. For example, app/v1beta1 StatefulSet specifies OnDelete by default. In apps/v1beta2 the spec.updateStrategy for all kinds defaults to RollingUpdate.
+
+#### CreatedBy Annotation is Deprecated


Annotation is Deprecated -> annotation is deprecated

Bradamant3 · 2017-09-28T02:53:06Z

Zach and I discussed the "objects"/"kinds" issue in Slack. The result in the next commit is the inevitable compromise that cannot possibly please everyone. Here's hoping it satisfies enough folks ;)

steveperry-53 · 2017-09-28T03:46:30Z

docs/reference/workloads-18-19.md

+### Release 1.9
+
+In Kubernetes 1.9, our goal is to address any feedback on the apps/v1beta2 group version and to to promote the group version to GA. The table below shows the kinds that we plan to deprecate and the kinds that will replace them.
+


to to -> to

steveperry-53 · 2017-09-28T03:49:37Z

@Bradamant3 @zacharysarah The recent changes look fine to me. (one case of to to)

Go ahead and merge this when you're ready. No need to get further approval from me.

Bradamant3 · 2017-09-28T16:29:17Z

Typo is fixed but commits are not squashed. lmk if I should squash and re-push.

zacharysarah · 2017-09-28T16:56:42Z

lmk if I should squash and re-push.

Probably easier just to squash when you merge.

@chenopis

* GC now supports non-core resources * Add two examples about how to analysis audits of kube-apiserver (#4264) * Deprecate system:nodes binding * [1.8] StatefulSet `initialized` annotation is now ignored. * inits the kubeadm upgrade docs addresses /issues/4689 * adds kubeadm upgrade cmd to ToC addresses /issues/4689 * add workload placement docs * ScaleIO - document udpate for 1.8 * Add documentation on storageClass.mountOptions and PV.mountOptions (#5254) * Add documentation on storageClass.mountOptions and PV.mountOptions * convert notes into callouts * Add docs for CustomResource validation add info about supported fields * advanced audit beta features (#5300) * Update job workload doc with backoff failure policy (#5319) Add to the Jobs documentation how to use the new backoffLimit field that limit the number of Pod failure before considering the Job as failed. * Documented additional AWS Service annotations (#4864) * Add device plugin doc under concepts/cluster-administration. (#5261) * Add device plugin doc under concepts/cluster-administration. * Update device-plugins.md * Update device-plugins.md Add meta description. Fix typo. Change bare metal deployment to manual deployment. * Update device-plugins.md Fix typo again. * Update page.version. (#5341) * Add documentation on storageClass.reclaimPolicy (#5171) * [Advanced audit] use new herf for audit-api (#5349) This tag contains all the changes in v1beta1 version. Update it now. * Added documentation around creating the InitializerConfiguration for the persistent volume label controller in the cloud-controller-manager (#5255) * Documentation for kubectl plugins (#5294) * Documentation for kubectl plugins * Update kubectl-plugins.md * Update kubectl-plugins.md * Updated CPU manager docs to match implementation. (#5332) * Noted limitation of alpha static cpumanager. * Updated CPU manager docs to match implementation. - Removed references to CPU pressure node condition and evictions. - Added note about new --cpu-manager-reconcile-period flag. - Added note about node allocatable requirements for static policy. - Noted limitation of alpha static cpumanager. * Move cpu-manager task link to rsc mgmt section. * init containers annotation removed in 1.8 (#5390) * Add documentation for TaintNodesByCondition (#5352) * Add documentation for TaintNodesByCondition * Update nodes.md * Update taint-and-toleration.md * Update daemonset.md * Update nodes.md * Update taint-and-toleration.md * Update daemonset.md * Fix deployments (#5421) * Document extended resources and OIR deprecation. (#5399) * Document extended resources and OIR deprecation. * Updated extended resources doc per reviews. * reverts extra spacing in _data/tasks.yml * addresses `kubeadm upgrade` review comments Feedback from @chenopis, @luxas, and @steveperry-53 addressed with this commit * HugePages documentation (#5419) * Update cpu-management-policies.md (#5407) Fixed the bad link. Modified "cpu" to "CPU". Added more 'yaml' as supplement. * Update RBAC docs for v1 (#5445) * Add user docs for pod priority and preemption (#5328) * Add user docs for pod priority and preemption * Update pod-priority-preemption.md * More updates * Update docs/admin/kubeadm.md for 1.8 (#5440) - Made a couple of minor wording changes (not strictly 1.8 related). - Did some reformatting (not strictly 1.8 related). - Updated references to the default token TTL (was infinite, now 24 hours). - Documented the new `--discovery-token-ca-cert-hash` and `--discovery-token-unsafe-skip-ca-verification` flags for `kubeadm join`. - Added references to the new `--discovery-token-ca-cert-hash` flag in all the default examples. - Added a new _Security model_ section that describes the security tradeoffs of the various discovery modes. - Documented the new `--groups` flag for `kubeadm token create`. - Added a note of caution under _Automating kubeadm_ that references the _Security model_ section. - Updated the component version table to drop 1.6 and add 1.8. - Update `_data/reference.yml` to try to get the sidebar fixed up and more consistent with `kubefed`. * Update StatefulSet Basics for 1.8 release (#5398) * addresses `kubeadm upgrade` review comments 2nd iteration review comments by @luxas * adds kubelet upgrade section to kubeadm upgrade * Fix a bulleted list on docs/admin/kubeadm.md. (#5458) I updated this doc yesterday and I was absolutely sure I fixed this, but I just saw that this commit got lost somehow. This was introduced recently in #5440. * Clarify the API to check for device plugins * Moving Flexvolume to separate out-of-tree section * addresses `kubeadm upgrade` review comments CC: @luxas * fixes kubeadm upgrade index * Update Stackdriver Logging documentation (#5495) * Re-update WordPress and MySQL PV doc to use apps/v1beta2 APIs (#5526) * Update statefulset concepts doc to use apps/v1beta2 APIs (#5420) * add document on kubectl's behavior regarding initializers (#5505) * Update docs/admin/kubeadm.md to cover self-hosting in 1.8. (#5497) This is a new beta feature in 1.8. * Update kubectl patch doc to use apps/v1beta2 APIs (#5422) * [1.8] Update "Run Applications" tasks to apps/v1beta2. (#5525) * Update replicated stateful application task for 1.8. * Update single instance stateful app task for 1.8. * Update stateless app task for 1.8. * Update kubectl patch task for 1.8. * fix the link of persistent storage (#5515) * update the admission-controllers.md index.md what-is-kubernetes.md link * fix the link of persistent storage * Add quota support for local ephemeral storage (#5493) * Add quota support for local ephemeral storage update the doc to this alpha feature * Update resource-quotas.md * Updated Deployments concepts doc (#5491) * Updated Deployments concepts doc * Addressed comments * Addressed more comments * Modify allocatable storage to ephemeral-storage (#5490) Update the doc to use ephemeral-storage instead of storage * Revamped concepts doc for ReplicaSet (#5463) * Revamped concepts doc for ReplicaSet * Minor changes to call out specific versions for selector defaulting and immutability * Addressed doc review comments * Remove petset documentations (#5395) * Update docs to use batch/v1beta1 cronjobs (#5475) * add federation job doc (#5485) * add federation job doc * Update job.md Edits for clarity and consistency * Update job.md Fixed a typo * update DaemonSet concept for 1.8 release (#5397) * update DaemonSet concept for 1.8 release * Update daemonset.md Fix typo. than -> then * Update bootstrap tokens doc for 1.8. (#5479) * Update bootstrap tokens doc for 1.8. This has some changes I missed when I was updating the main kubeadm documention: - Bootstrap tokens are now beta, not alpha (kubernetes/enhancements#130) - The apiserver flag to enable the authenticator changedin 1.8 (kubernetes/kubernetes#51198) - Added `auth-extra-groups` documentaion (kubernetes/kubernetes#50933) - Updated the _Token Management with `kubeadm`_ section to link to the main kubeadm docs, since it was just duplicated information. * Update bootstrap-tokens.md * Updated the Cassandra tutorial to use apps/v1beta2 (#5548) * add docs for AllowPrivilegeEscalation (#5448) Signed-off-by: Jess Frazelle <acidburn@microsoft.com> * Add local ephemeral storage alpha feature in managing compute resource (#5522) * Add local ephemeral storage alpha feature in managing compute resource Since 1.8, we add the local ephemeral storage alpha feature as one resource type to manage. Add this feature into the doc. * Update manage-compute-resources-container.md * Update manage-compute-resources-container.md * Update manage-compute-resources-container.md * Update manage-compute-resources-container.md * Update manage-compute-resources-container.md * Update manage-compute-resources-container.md * Added documentation for Metrics Server (#5560) * authorization: improve authorization debugging docs (#5549) * Document mount propagation (#5544) * Update /docs/setup/independent/create-cluster-kubeadm.md for 1.8. (#5524) This introduction needed a couple of small tweaks to cover the `--discovery-token-ca-cert-hash` flag added in kubernetes/kubernetes#49520 and some version bumps. * Add task doc for alpha dynamic kubelet configuration (#5523) * Fix input/output of selfsubjectaccess review (#5593) * Add docs for implementing resize (#5528) * Add docs for implementing resize * Update admission-controllers.md * Added link to PVC section * minor typo fixes * Update NetworkPolicy concept guide with egress and CIDR changes (#5529) * update zookeeper tutorial for 1.8 release * add doc for hostpath type (#5503) * Federated Hpa feature doc (#5487) * Federated Hpa feature doc * Federated Hpa feature doc review fixes * Update hpa.md * Update hpa.md * update cloud controller manager docs for v1.8 * Update cronjob with defaults information (#5556) * Kubernetes 1.8 reference docs (#5632) * Kubernetes 1.8 reference docs * Kubectl reference docs for 1.8 * Update side bar with 1.8 kubectl and api ref docs links * remove petset.md * update on state of HostAlias in 1.8 with hostNetwork Pod support (#5644) * Fix cron job deletion section (#5655) * update imported docs (#5656) * Add documentation for certificate rotation. (#5639) * Link to using kubeadm page * fix the command output fix the command output * fix typo in api/resources reference: "Worloads" * Add documentation for certificate rotation. * Create TOC entry for cloud controller manager. (#5662) * Updates for new versions of API types * Followup 5655: fix link to garbage collection (#5666) * Temporarily redirect resources-reference to api-reference. (#5668) * Update config for 1.8 release. (#5661) * Update config for 1.8 release. * Address reviewer comments. * Switch references in HPA docs from alpha to beta (#5671) The HPA docs still referenced the alpha version. This switches them to talk about v2beta1, which is the appropriate version for Kubernetes 1.8 * Deprecate openstack heat (#5670) * Fix typo in pod preset conflict example Move container port definition to the correct line. * Highlight openstack-heat provider deprecation The openstack-heat provider for kube-up is being deprecated and will be removed in a future release. * Temporarily fix broken links by redirecting. (#5672) * Fix broken links. (#5675) * Fix render of code block (#5674) * Fix broken links. (#5677) * Add a small note about auto-bootstrapped CSR ClusterRoles (#5660) * Update kubeadm install doc for v1.8 (#5676) * add draft workloads api content for 1.8 (#5650) * add draft workloads api content for 1.8 * edits per review, add tables, for 1.8 workloads api doc * fix typo * Minor fixes to kubeadm 1.8 upgrade guide. (#5678) - The kubelet upgrade instructions should be done on every host, not just worker nodes. - We should just upgrade all packages, instead of calling out kubelet specifically. This will also upgrade kubectl, kubeadm, and kubernetes-cni, if installed. - Draining nodes should also ignore daemonsets, and master errors can be ignored. - Make sure that the new kubeadm download is chmoded correctly. - Add a step to run `kubeadm version` to verify after downloading. - Manually approve new kubelet CSRs if rotation is enabled (known issue). * Release 1.8 (#5680) * Fix versions for 1.8 API ref docs * Updates for 1.8 kubectl reference docs * Kubeadm /docs/admin/kubeadm.md cleanup, editing. (#5681) * Update docs/admin/kubeadm.md (mostly 1.8 related). This is Fabrizio's work, which I'm committing along with my edits (in a commit on top of this). * A few of my own edits to clarify and clean up some Markdown.

Bradamant3 added this to the 1.8 milestone Sep 27, 2017

Bradamant3 assigned steveperry-53 Sep 27, 2017

Bradamant3 requested review from zacharysarah and steveperry-53 September 27, 2017 05:39

k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Sep 27, 2017

steveperry-53 reviewed Sep 27, 2017

View reviewed changes

steveperry-53 added the Docs LGTM label Sep 27, 2017

zacharysarah reviewed Sep 27, 2017

View reviewed changes

tengqm mentioned this pull request Sep 28, 2017

Remove a bad example for selector defaulting #5665

Merged

JENNIFER RONDEAU added 2 commits September 27, 2017 19:54

add draft workloads api content for 1.8

681a2a0

edits per review, add tables, for 1.8 workloads api doc

4fe02b4

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Sep 28, 2017

Bradamant3 requested a review from kow3ns September 28, 2017 03:02

steveperry-53 reviewed Sep 28, 2017

View reviewed changes

steveperry-53 assigned Bradamant3 and zacharysarah Sep 28, 2017

fix typo

dc90d57

chenopis merged commit 2f56f12 into kubernetes:release-1.8 Sep 28, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

add draft workloads api content for 1.8 #5650

add draft workloads api content for 1.8 #5650

Bradamant3 commented Sep 27, 2017 •

edited by k8s-reviewable

Loading

k8sio-netlify-preview-bot commented Sep 27, 2017 •

edited

Loading

steveperry-53 Sep 27, 2017

steveperry-53 Sep 27, 2017

steveperry-53 Sep 27, 2017

zacharysarah Sep 27, 2017

steveperry-53 commented Sep 27, 2017

steveperry-53 commented Sep 27, 2017

zacharysarah left a comment •

edited

Loading

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

Bradamant3 Sep 27, 2017

zacharysarah Sep 27, 2017

steveperry-53 Sep 27, 2017

Bradamant3 Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

zacharysarah Sep 27, 2017

Bradamant3 commented Sep 28, 2017

steveperry-53 Sep 28, 2017

steveperry-53 commented Sep 28, 2017

Bradamant3 commented Sep 28, 2017

zacharysarah commented Sep 28, 2017

		- In the 1.8 release, we introduce the apps/v1beta2 API group and version. This beta version of the core workload API contains the current version of Deployment, DaemonSet, ReplicaSet, and StatefulSet, and it is the version we plan to promote, provided the feedback is positive, to GA in the 1.9 release.

		- In the 1.9 release, we plan to introduce the apps/v1 API. We intend to promote the you also mentioned that we might want to not mark everything in types.go with +DEPRECATED should we clean this up prior to approval or apps/v1beta2 group version in its entirety to apps/v1 and to deprecate apps/v1beta2 at that time.

		#### Immutable Selectors

		Selector mutation, while allowing for some use cases like promotable Deployment canaries, the core workloads controller do not, in the general case, handle selector mutation gracefully, and we have always strongly cautioned users against it.

		We believe that there are better ways to support features like promotable canaries and orchestrated Pod relabeling, but, if restricted selector mutation is a necessary feature for our users, we can relax immutability prior to GA without breaking backward compatibility.

		The development of features like promotable canaries, orchestrated Pod relabeling,and restricted selector mutability is driven by demand signals from our users. If you are currently modifying the selectors of your core workload API objects, please tell us about your use case in a GitHub issue, or by participating in SIG-apps.

		@@ -0,0 +1,57 @@
		---
		title: Workloads API changes in version 1.8 and 1.9


		## Overview

		The Kubernetes core workload API consists of the Deployment, DaemonSet, ReplicaSet, and StatefulSet API objects. In order to provide a stable API for users to orchestrate their workloads, we are prioritizing promoting the core workload API to GA. The batch workload API (Job and CronJob), while also important, is not part of this effort, and it will have a separate path to GA stability.


		- If you are using kinds from the extensions/v1beta1 or apps/v1beta1 group versions, you can wait to migrate existing code until after the release of the apps/v1 group version.

		- If there are features in the apps/v1beta2 group version that you want to consume, you may migrate to this group version prior to the apps/v1 release.


		- If there are features in the apps/v1beta2 group version that you want to consume, you may migrate to this group version prior to the apps/v1 release.

		- You should develop all new code againsts the latest stable release.


		### Migrating to apps/v1beta2

		This section provides information on migrating to the apps/v1beta2 group version. It covers general changes to the core workloads API kinds. For changes that affect a specific kind (e.g. defaults), you should consult the reference documentation for the kind.


		User feedback led us to determine that, as it is incompatible with strategic merge patch and kubectl apply, defaulting the value of a field from the value of another field of the same object is an anti-pattern.

		#### Immutable Selectors


		Selector mutation, while allowing for some use cases like promotable Deployment canaries, the core workloads controller do not, in the general case, handle selector mutation gracefully, and we have always strongly cautioned users against it.

		To provide a consistent, usable, and stable API, selectors have been made immutable for all kinds in the apps/v1beta2 group and version.


		The development of features like promotable canaries, orchestrated Pod relabeling,and restricted selector mutability is driven by demand signals from our users. If you are currently modifying the selectors of your core workload API objects, please tell us about your use case in a GitHub issue, or by participating in SIG-apps.

		#### Default Rolling Updates


		#### Default Rolling Updates

		Prior to apps/v1beta2, some kinds defaulted the spec.updateStrategy to a strategy other than RollingUpdate. For example, app/v1beta1 StatefulSet specifies OnDelete by default. In apps/v1beta2 the spec.updateStrategy for all kinds defaults to RollingUpdate.


		Prior to apps/v1beta2, some kinds defaulted the spec.updateStrategy to a strategy other than RollingUpdate. For example, app/v1beta1 StatefulSet specifies OnDelete by default. In apps/v1beta2 the spec.updateStrategy for all kinds defaults to RollingUpdate.

		#### CreatedBy Annotation is Deprecated

		### Release 1.9

		In Kubernetes 1.9, our goal is to address any feedback on the apps/v1beta2 group version and to to promote the group version to GA. The table below shows the kinds that we plan to deprecate and the kinds that will replace them.

add draft workloads api content for 1.8 #5650

add draft workloads api content for 1.8 #5650

Conversation

Bradamant3 commented Sep 27, 2017 • edited by k8s-reviewable Loading

k8sio-netlify-preview-bot commented Sep 27, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

steveperry-53 commented Sep 27, 2017

steveperry-53 commented Sep 27, 2017

zacharysarah left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bradamant3 commented Sep 28, 2017

Choose a reason for hiding this comment

steveperry-53 commented Sep 28, 2017

Bradamant3 commented Sep 28, 2017

zacharysarah commented Sep 28, 2017

Bradamant3 commented Sep 27, 2017 •

edited by k8s-reviewable

Loading

k8sio-netlify-preview-bot commented Sep 27, 2017 •

edited

Loading

zacharysarah left a comment •

edited

Loading