Removing Opaque Integer Resources

[mburke5678]

Per #19347

I see that Opaque Integer Resources are removed from 1.9 version as per the link here kubernetes/enhancements#76 (comment) so documentation related to Opaque Integer Resources should be removed.

Verified by @rphillips in Slack: https://coreos.slack.com/archives/CK1AE4ZCK/p1581020513181400

[openshift-docs-preview-bot]

The preview will be available shortly at:

• https://nodes-remove-opaque--ocpdocs.netlify.com/

[mburke5678]

@sunilcio Is this a PR you can review?

[mburke5678]

Files removed from 3.x via #19593

[vikram-redhat]

Anytime we remove or change a previously documented (and supported) feature we need to follow the steps outlined recently to help support these changes and help make the transition.

We need acks from Product Experience, Docs, PM, Eng and QE. We also need to send out information about this change to openshift-sme and aos-devel, before we make this change, and once the change is done.

@sferich888 and/or @reestr do you ack this change from both 3.11 and 4.x docs?
@xltian is this ok from QE?

@mburke5678 - Since eng raised this issue, happy to consider this as an ack. Not sure which PM can ack this change though. Can you confirm with eng?

[sferich888]

Based on kubernetes/enhancements#76 (comment) removing this from 3.10 and 3.11 docs should be OK, given that upstream kube dropped support for this resource in 1.9 (3.9)

[vikram-redhat]

@tkatarki are you ok with us removing this from the docs for both 3.x and 4.x?

[xltian]

@sunilcio Can you please review from QE? Thanks

[jhou1]

@weinliu PTAL

[weinliu]

Anytime we remove or change a previously documented (and supported) feature we need to follow the steps outlined recently to help support these changes and help make the transition.

We need acks from Product Experience, Docs, PM, Eng and QE. We also need to send out information about this change to openshift-sme and aos-devel, before we make this change, and once the change is done.

@sferich888 and/or @reestr do you ack this change from both 3.11 and 4.x docs?
@xltian is this ok from QE?

@mburke5678 - Since eng raised this issue, happy to consider this as an ack. Not sure which PM can ack this change though. Can you confirm with eng?

Removing this is ok for QE as per:

Removed opaque integer resources (deprecated in v1.8) #55103
kubernetes/kubernetes#55103

[mburke5678]

@rphillips do you ack this change from both 3.11 and 4.x docs?

[mburke5678]

@tkatarki @rphillips do you ack this change from both 3.11 and 4.x docs?

[mburke5678]

@tkatarki Approved via Slack.

[rphillips]

/lgtm
Thanks!

[mburke5678]

/cherrypick enterprise-4.1

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #20344

In response to this:

/cherrypick enterprise-4.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mburke5678]

/cherrypick enterprise-4.2

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #20345

In response to this:

/cherrypick enterprise-4.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mburke5678]

/cherrypick enterprise-4.3

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #20346

In response to this:

/cherrypick enterprise-4.3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mburke5678]

/cherrypick enterprise-4.4

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #20347

In response to this:

/cherrypick enterprise-4.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.