Skip to content

Conversation

@mburke5678
Copy link
Contributor

@mburke5678 mburke5678 commented Jul 23, 2020

https://bugzilla.redhat.com/show_bug.cgi?id=1860289

Reorganized the information; updated feature set list; added console instructions; renamed files for consistency.

Preview: https://deploy-preview-24132--osdocs.netlify.app/openshift-enterprise/latest/nodes/clusters/nodes-cluster-enabling-features.html

Wording for unsupported feature sets from: https://github.com/openshift/machine-config-operator/blob/master/vendor/github.com/openshift/api/config/v1/types_feature.go#L41

LatencySentitive feature set no longer required for Topology Manager per https://access.redhat.com/solutions/5807641 and https://bugzilla.redhat.com/show_bug.cgi?id=1921160

LatencySensitive feature set does not affect any other feature and can be removed from docs: https://coreos.slack.com/archives/CQNBUEVM2/p1618238903115900?thread_ts=1616327266.083200&cid=CQNBUEVM2

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 23, 2020
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 22, 2020
@mburke5678 mburke5678 force-pushed the fix-feature-gate-numbers branch from fb8a7fd to f07a670 Compare October 22, 2020 20:57
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 22, 2020
@mburke5678
Copy link
Contributor Author

mburke5678 commented Oct 22, 2020

@sttts Here is a second attempt at reworking the feature gates docs. WDYT?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do I know the set of feature gates I can set?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is no easier way than this to reach a config CR? @jhadvig can you confirm?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above: this needs a link to all possible values.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

double "enables"

@sttts
Copy link

sttts commented Oct 23, 2020

Nits and missing links.

@mburke5678
Copy link
Contributor Author

@xltian Can you please assign this issue to a QE resource for review? Thank you!

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from https://github.com/openshift/api/blob/master/config/v1/types_feature.go, I saw "IPv6DualStackNoUpgrade enables dual-stack. Turning this feature set on IS NOT SUPPORTED". Since turn this feature set on is not supported, we should remove IPv6DualStackNoUpgrade feature set.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sttts ^^

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc networking team @danwinship

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what the rules about documenting feature sets are. In this case, we don't want the featureset to be used by people who don't already know about it, so not documenting it seems like the right thing.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from https://docs.openshift.com/container-platform/4.5/nodes/clusters/nodes-cluster-enabling-features.html#feature-gate-features_nodes-cluster-enabling ,do we need add Technology Preview features like MachineHealthCheck and LocalStorageCapacityIsolation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lyman9966 @sttts The list came from here: https://github.com/openshift/api/blob/release-4.6/config/v1/types_feature.go#L29
Stefan, these are the 4 feature sets that the user can enable?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678 I think you misunderstood me. "https://docs.openshift.com/container-platform/4.5/nodes/clusters/nodes-cluster-enabling-features.html#feature-gate-features_nodes-cluster-enabling" show us there are 4 features affected by feature set "TechPreviewNoUpgrade", such as "RotateKubeletServerCertificate","SupportPodPidsLimit","MachineHealthCheck","LocalStorageCapacityIsolation". Yet your doc lack the latter two.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lyman9966 MachineHealthCheck went GA in 4.3: https://docs.openshift.com/container-platform/4.3/machine_management/deploying-machine-health-checks.html
It appears that LocalStorageCapacityIsolation was enabled at some point https://github.com/openshift/api/pull/462/files

I assume this means that the TechPreviewNoUpgrade feature gate would not enable these features.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678 , Okay, then "MachineHealthCheck" and "LocalStorageCapacityIsolation" doesn't belong to TechPreview feature, so they can be removed.

@sttts
Copy link

sttts commented Nov 2, 2020

General question: why do we place feature gates under node configuration in the docs? We had a similar case with audit and moved it out from there. Both audit and features gates are cluster-wide settings, and have nothing to do with nodes in particular.

@lyman9966
Copy link

General question: why do we place feature gates under node configuration in the docs? We had a similar case with audit and moved it out from there. Both audit and features gates are cluster-wide settings, and have nothing to do with nodes in particular.

@sttts I see the feature gates under Node->Working with clusters chapter, It seems in 4.x, we move cluster-wide settings to Node chapter.

@mburke5678
Copy link
Contributor Author

@sttts I would guess that Feature Gates was added to nodes (likely by me) because in 3.x the user could activate feature gates by node in addition to the entire cluster.
Enabling feature gates is also included in the Post-installation cluster tasks topic.
https://docs.openshift.com/container-platform/4.6/post_installation_configuration/cluster-tasks.html#nodes-cluster-enabling-features-cluster_post-install-cluster-tasks
If you can think of another or a better location for this information, please met me know!

@mburke5678
Copy link
Contributor Author

@sferich888 There has been discussion here about whether we want to document Feature Gates that enable unsupported features in the end user docs. What do you think?

@mburke5678 mburke5678 changed the title updating feature gates in master to match branches updating feature gates docs Nov 10, 2020
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The following is commented-out. No need for review at this time

@mburke5678
Copy link
Contributor Author

@sferich888 There has been discussion here about whether we want to document Feature Gates that enable unsupported features in the end user docs. What do you think?

@mburke5678
Copy link
Contributor Author

@sferich888 There has been discussion here about whether we want to document Feature Gates that enable unsupported features in the end user docs. What do you think?

@mburke5678
Copy link
Contributor Author

@reestr Can you weigh in here in Eric Rich's absence? Do we want to document Feature Gates that enable unsupported features in the end user docs?

@mburke5678 mburke5678 force-pushed the fix-feature-gate-numbers branch 2 times, most recently from e1a745b to 43206be Compare January 4, 2021 19:16
@mburke5678
Copy link
Contributor Author

mburke5678 commented Mar 18, 2021

@sferich888 Do we want to document Feature Gates that enable unsupported features in the end user docs?

|IPv6DualStackNoUpgrade
|Enables the dual-stack networking mode in your cluster. Dual-stack networking supports the use of IPv4 and IPv6 simultaneously. Turning on this feature set is not supported, cannot be undone, and prevents upgrades.

@lyman9966 said: Turning this feature set on IS NOT SUPPORTED". Since turn this feature set on is not supported, we should remove IPv6DualStackNoUpgrade feature set.

@sferich888
Copy link
Contributor

@mburke5678 documenting the 'available' feature gates 'supported' or 'unsupported' is fine, so long as we 'clearly' (boldly) call out what 'features' are 'experimental' and or 'risky' for production usecases.

The term 'unsupported' (or inversely - supported) is a loaded term, because it means many things to many different people (or classes of users), so I would 'try and avoid it'. however in your 'statement' what you say is fine as your clearly outlining that enabling this / blocks upgrades.

@mburke5678
Copy link
Contributor Author

mburke5678 commented Mar 30, 2021

@sferich888 @lyman9966 I can add the term experimental, as we do use that in the docs. I am not sure if IPv6DualStackNoUpgrade is officially experimental (or who decides something is experimental and how it is decided).

@lyman9966 Can I ask you to please take another look at the udated warnings for TechPreviewNoUpgrade or IPv6DualStackNoUpgrade.

@netlify
Copy link

netlify bot commented Mar 30, 2021

Deploy preview for osdocs ready!

Built with commit b0191852e5ecca65b02d8a87d421fb176b09534a

https://deploy-preview-24132--osdocs.netlify.app

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2021
@mburke5678 mburke5678 force-pushed the fix-feature-gate-numbers branch from 18d9386 to 81adaa2 Compare April 9, 2021 14:45
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Apr 9, 2021
@openshift-ci-robot
Copy link

New changes are detected. LGTM label has been removed.

Copy link
Contributor

@lbarbeevargas lbarbeevargas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job on this! Just a few comments per the OCP guidelines and some small wording suggestions. :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you are specifying say that this is a custom resource, what do you think of:

s/the Feature Gate custom resource (CR)/the FeatureGate custom resource (CR)/.

It is also in backticks in modules/nodes-cluster-enabling-features-cli.adoc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I caught that one, but missed the others. D'oh!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar comment as for the module intro above:
s/Feature Gate CR/FeatureGate CR/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we recently switched from bold to italics to emphasize text. s/*not supported*/_not supported_/
Per the doc guidelines:

Use of underscores for general emphasis is allowed but should only be used very sparingly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am now watching the Doc Guidelines. Hope I get notified of such changes!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the feature set need to be in backticks here? s/SupportPodPidsLimit/SupportPodPidsLimit/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lbarbeevargas That is the name of a feature in the feature set. I don't think we mark-up feature names(??). We don't in Tech Preview notes, apparently: https://github.com/openshift/openshift-docs/pull/13878/files#diff-99eeb6425c261c0f96653039df58187866a5429c67f34e40c6364f0bd3d5e6a0L10

Copy link
Contributor

@lbarbeevargas lbarbeevargas Apr 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678 The feature names caught my attention here because they are in PascalCase, whereas the feature name (:FeatureName: variable) example linked in the guidelines is spelled out.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lbarbeevargas The Pascal case spelling is the common usage on the internet. But, the Kubernetes docs use Pascal case in the feature gates docs and Pod PID limits in the release notes.
What if we go with both, too? Pod PID limits (SupportPodPidsLimit)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't come across this situation before, but LGTM if it makes sense to the other reviewers. 👍 If going with the dual format, the first bullet can be updated as well:

link:https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/#certificate-rotation[Certificate rotation (RotateKubeletServerCertificate)]. Enables the rotation of the server TLS certificate on the kubelet.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Feature Gate CR/FeatureGate CR/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same feedback as for the CLI module: s/enable feature sets for all the nodes/enable feature sets for all of the nodes/
or
/enable feature sets for all nodes/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nit for these two bullets:

  • IPv6DualStackNoUpgrade enables the dual-stack networking mode.
  • TechPreviewNoUpgrade enables specific Technology Preview features.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nit for these two bullets:

  • IPv6DualStackNoUpgrade enables the dual-stack networking mode.
  • TechPreviewNoUpgrade enables specific Technology Preview features.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the full assembly path be here? nodes/clusters/nodes-cluster-enabling-features.adoc

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I moved these files around a lot when converting from 3.11 to 4.x. I'm sure there are others just like this,

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the full assembly path be here? nodes/clusters/nodes-cluster-enabling-features.adoc

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/FeatureGates/feature gates/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small rewording suggestion:

You can enable Technology Preview features for all nodes in your cluster by editing the FeatureGate custom resource in the openshift-config project.

@lbarbeevargas lbarbeevargas added the peer-review-done Signifies that the peer review team has reviewed this PR label Apr 9, 2021
@mburke5678
Copy link
Contributor Author

Separate PR required for 4.5 as LatencySensitive is still required for Topology Manager.

@mburke5678 mburke5678 force-pushed the fix-feature-gate-numbers branch from d1d10f4 to 7ea7680 Compare April 12, 2021 15:35
@lyman9966
Copy link

the Topololgy Manager part LGTM. I mean for bug https://bugzilla.redhat.com/show_bug.cgi?id=1921160

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we want to remove this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678
Copy link
Contributor Author

New TP features for 4.8??
https://issues.redhat.com/browse/STOR-361

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.6 branch/enterprise-4.7 branch/enterprise-4.8 peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants