Add blog post about upcoming API removals by vllry · Pull Request #15203 · kubernetes/website

vllry · 2019-06-29T17:55:48Z

Adds a blog post about the deprecated APIs that are due for removal soon in Kubernetes.

vllry · 2019-06-29T17:57:28Z

I wanted to clarify - are the "actual removal" vs "not enabled" timelines different? It would be nice to specify.

vllry · 2019-06-29T17:58:10Z

vllry · 2019-06-29T17:59:39Z

This is also at the "minimum level of approachability" I feel comfortable publishing. I know this will be a mysterious/scary announcement for many users. I'm not sure how much more approachable I should aim to make it - @zacharysarah I would appreciate your guidance there.

netlify · 2019-06-29T18:06:30Z

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 17f17d3

https://deploy-preview-15203--kubernetes-io-master-staging.netlify.com

netlify · 2019-06-29T18:07:07Z

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 537e76e

https://deploy-preview-15203--kubernetes-io-master-staging.netlify.com

dims · 2019-06-29T22:25:39Z

/cc @liggitt

geekygirldawn

This is great! I only made a few tiny, nit-picky suggestions.

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

geekygirldawn · 2019-07-01T09:43:04Z

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

+re-organized or upgraded. When this happens, the old API is deprecated, and then
+eventually removed.
+
+There are **4** sets of resources with APIs that are deprecated, will be stop


maybe this would be better as

... are deprecated, and will stop being ...

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

liggitt · 2019-07-01T15:32:11Z

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

+your configuration and integrations now!
+
+* Change YAML files to use the newer APIs.
+  * Update the `apiVersion` field.


For Ingress, this is sufficient.

For the workload APIs, there is more involved to get objects you can create. At minimum:

change apiVersion to apps/v1

populate spec.selector.matchLabels with the contents of spec.template.metadata.labels if spec.selector does not already exist

populate metadata.labels with the contents of spec.template.metadata.labels if metadata.labels does not already exist

kubectl convert -f ... --output-version apps/v1 will also perform the conversion for you, if everything in the manifest can be converted to apps/v1.

That said, an automated conversion will also carry over some sub-optimal defaults that were improved in apps/v1. A few examples:

Deployments changed spec.revisionHistoryLimit to default to 10 to avoid infinite replicaset growth on repeated rollouts. Old versions defaulted to MAX_INT.

DaemonSets changed default update strategy from OnDelete to RollingUpdate

@kubernetes/sig-apps-api-reviews is there a comprehensive doc of the differences in defaults between apps/v1 and earlier versions, and a migration guide?

liggitt · 2019-07-01T15:45:21Z

/hold

wanted to make sure #15203 (comment) was addressed before merge

zacharysarah

@vllry You're off to a great start! ✨ I left some edits for clarity and mechanics.

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

zacharysarah · 2019-07-03T05:28:27Z

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

+* DaemonSet, Deployment, StatefulSet, and ReplicaSet
+* Ingress
+
+None of these resources are being removed from Kubernetes. NetworkPolicies,


None of these resources are being removed from Kubernetes.

This is a great thing to specify. 👍

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

zacharysarah · 2019-07-03T05:44:37Z

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

+
+* Change YAML files to use the newer APIs.
+  * Update the `apiVersion` field.
+* Update custom integrations and controllers to use the newer APIs.


Remove periods from the ends of bullet points.

If "call" is more specifically accurate, s/use/call.

content/en/blog/_posts/2019-06-29-some-apis-are-being-deprecated.md

vllry · 2019-07-09T01:24:08Z

I've addressed all current comments, but should have another pass. It's a separate commit for ease of review, but I can squash if folks prefer.

CC @zacharysarah @liggitt

content/en/blog/_posts/2019-07-09-some-apis-are-being-deprecated.md

liggitt · 2019-07-09T18:13:54Z

one suggestion on the convert command, technical content lgtm otherwise

vllry · 2019-07-09T18:26:10Z

one suggestion on the convert command, technical content lgtm otherwise

Done, thanks!

onlydole

Great topic, well written and looks good to me! 👍

vllry · 2019-07-11T06:27:36Z

I'm not sure how to address the failing tests - I'm guessing it's a quotation issue in the metadata.

onlydole · 2019-07-11T19:49:01Z

content/en/blog/_posts/2019-07-09-some-apis-are-being-deprecated.md

@@ -0,0 +1,89 @@
+---
+layout: blog
+title: 'APIs Deprecating Soon: Here\'s What You Need to Know'


Might need to be ”APIs deprecating Soon: Here’s What You Need To Know”

nit, these were deprecated ~years ago... they're being removed in 1.16

Changed accordingly.

content/en/blog/_posts/2019-07-09-some-apis-are-being-deprecated.md

zacharysarah · 2019-07-11T22:11:09Z

@vllry 👋

I'm not sure how to address the failing tests - I'm guessing it's a quotation issue in the metadata.

Based on this error, that seems accurate:

11:26:25 AM: Error: Error building site: "/opt/build/repo/content/en/blog/_posts/2019-07-09-some-apis-are-being-deprecated.md:2:1": failed to unmarshal YAML: yaml: line 1: did not find expected key

Maybe try this, inclusive of @liggitt's feedback about timeframe:

title: 'Removing APIs Soon: What You Need to Know'

vllry · 2019-07-15T20:14:19Z

@zacharysarah I fixed the build, will squash commits with your approval.

zacharysarah · 2019-07-17T13:52:09Z

@vllry Thanks for your patience! LGTM, squash away.

/lgtm

vllry · 2019-07-17T15:14:29Z

There we are, also bumped the date again. Sorry that took so many back and forths!

@liggitt can we remove the hold?

vllry · 2019-07-17T15:16:45Z

Ugh the rebase dropped some edits, I'll fix it when I get to the office.

vllry · 2019-07-18T16:28:21Z

Re-bumped the date.

@kbarnard10 / @castrojo ?

kbarnard10 · 2019-07-18T16:40:39Z

/lgtm
/approve
@vllry Please remove the hold once you're ready to publish!

k8s-ci-robot · 2019-07-18T16:41:22Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kbarnard10

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~content/en/blog/OWNERS~~ [kbarnard10]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

vllry · 2019-07-18T16:51:12Z

/hold cancel

🚀

k8s-ci-robot requested review from onlydole and vonguard June 29, 2019 17:56

k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 29, 2019

k8s-ci-robot assigned castrojo and zacharysarah Jun 29, 2019

vllry force-pushed the api-removal-timeline branch from 17f17d3 to 216549e Compare June 29, 2019 18:01

k8s-ci-robot requested a review from liggitt June 29, 2019 22:25

vllry force-pushed the api-removal-timeline branch from 216549e to 39bce56 Compare June 29, 2019 22:34

geekygirldawn reviewed Jul 1, 2019

View reviewed changes

liggitt reviewed Jul 1, 2019

View reviewed changes

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 1, 2019

zacharysarah suggested changes Jul 3, 2019

View reviewed changes

vllry changed the title ~~WIP: Add blog post about upcoming API removals~~ Add blog post about upcoming API removals Jul 9, 2019

k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 9, 2019

vllry force-pushed the api-removal-timeline branch from dd24535 to ca88f06 Compare July 9, 2019 01:33

liggitt reviewed Jul 9, 2019

View reviewed changes

content/en/blog/_posts/2019-07-09-some-apis-are-being-deprecated.md Outdated Show resolved Hide resolved

kbarnard10 self-assigned this Jul 9, 2019

onlydole approved these changes Jul 10, 2019

View reviewed changes

onlydole reviewed Jul 11, 2019

View reviewed changes

content/en/blog/_posts/2019-07-09-some-apis-are-being-deprecated.md Show resolved Hide resolved

vllry force-pushed the api-removal-timeline branch from df4f179 to ee847a9 Compare July 15, 2019 19:53

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 17, 2019

vllry force-pushed the api-removal-timeline branch from ee847a9 to ce7552d Compare July 17, 2019 15:11

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 17, 2019

vllry force-pushed the api-removal-timeline branch 2 times, most recently from 37be202 to 8efdf19 Compare July 17, 2019 15:13

vllry changed the title ~~Add blog post about upcoming API removals~~ Do not merge: Add blog post about upcoming API removals Jul 17, 2019

vllry force-pushed the api-removal-timeline branch from 8efdf19 to 04aa97c Compare July 17, 2019 17:23

vllry changed the title ~~Do not merge: Add blog post about upcoming API removals~~ Add blog post about upcoming API removals Jul 17, 2019

Added English blog on API removal timelines in 1.16

537e76e

vllry force-pushed the api-removal-timeline branch from 04aa97c to 537e76e Compare July 18, 2019 16:27

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 18, 2019

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 18, 2019

k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 18, 2019

k8s-ci-robot merged commit 0225023 into kubernetes:master Jul 18, 2019

Conversation

vllry commented Jun 29, 2019

Uh oh!

vllry commented Jun 29, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vllry commented Jun 29, 2019

Uh oh!

vllry commented Jun 29, 2019

Uh oh!

netlify bot commented Jun 29, 2019

Uh oh!

netlify bot commented Jun 29, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dims commented Jun 29, 2019

Uh oh!

geekygirldawn left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

geekygirldawn Jul 1, 2019

Choose a reason for hiding this comment

Uh oh!

Uh oh!

liggitt Jul 1, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

liggitt commented Jul 1, 2019

Uh oh!

zacharysarah left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

zacharysarah Jul 3, 2019

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

zacharysarah Jul 3, 2019

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

vllry commented Jul 9, 2019

Uh oh!

Uh oh!

liggitt commented Jul 9, 2019

Uh oh!

vllry commented Jul 9, 2019

Uh oh!

onlydole left a comment

Choose a reason for hiding this comment

Uh oh!

vllry commented Jul 11, 2019

Uh oh!

onlydole Jul 11, 2019

Choose a reason for hiding this comment

Uh oh!

liggitt Jul 11, 2019

Choose a reason for hiding this comment

Uh oh!

vllry Jul 12, 2019

Choose a reason for hiding this comment

Uh oh!

Uh oh!

zacharysarah commented Jul 11, 2019

Uh oh!

vllry commented Jul 15, 2019

Uh oh!

zacharysarah commented Jul 17, 2019

Uh oh!

vllry commented Jul 17, 2019

Uh oh!

vllry commented Jul 17, 2019

Uh oh!

vllry commented Jun 29, 2019 •

edited

Loading

netlify bot commented Jun 29, 2019 •

edited

Loading

liggitt Jul 1, 2019 •

edited

Loading