Use Optional: instead

[jboxman]

Always use Optional:.

[netlify]

Deploy preview for osdocs ready!

Built with commit f37791b

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

[bergerhoffer]

Actual changes look good, but have two additional pieces of feedback:

1. I don't see in our guidelines that "Optional:" is preferred, though I remember talking about this, so I'm surprised that it's not. If we're asking people to use that over other ways, we should add it as a guideline. Would you mind doing that in a separate PR?
2. I would backport this as far as possible, just to avoid future merge conflicts for others.

[jboxman]

@bergerhoffer, from what I gather, this came from ISG and in the new edition appears on page 185.

[bergerhoffer]

@bergerhoffer, from what I gather, this came from ISG and in the new edition appears on page 185.

Awesome, I hadn't caught that in the update. That's good enough for me then, thanks!

[jboxman]

/cherry-pick enterprise-4.8

[openshift-cherrypick-robot]

@jboxman: new pull request created: #30864

Details

In response to this:

/cherry-pick enterprise-4.8

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.

[jboxman]

/cherry-pick enterprise-4.7

[openshift-cherrypick-robot]

@jboxman: new pull request created: #30865

Details

In response to this:

/cherry-pick enterprise-4.7

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.

[jboxman]

/cherry-pick enterprise-4.6

[openshift-cherrypick-robot]

@jboxman: #30835 failed to apply on top of branch "enterprise-4.6":

Applying: Use Optional: instead
Using index info to reconstruct a base tree...
M	modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc
M	modules/ipi-install-node-requirements.adoc
M	modules/virt-confirming-policy-updates-on-nodes.adoc
M	modules/virt-creating-vm-wizard-web.adoc
M	modules/virt-creating-vm-yaml-web.adoc
M	updating/updating-cluster-rhel-compute.adoc
Falling back to patching base and 3-way merge...
Auto-merging updating/updating-cluster-rhel-compute.adoc
Auto-merging modules/virt-creating-vm-yaml-web.adoc
Auto-merging modules/virt-creating-vm-wizard-web.adoc
CONFLICT (content): Merge conflict in modules/virt-creating-vm-wizard-web.adoc
Auto-merging modules/virt-confirming-policy-updates-on-nodes.adoc
Auto-merging modules/ipi-install-node-requirements.adoc
Auto-merging modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use Optional: instead
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick enterprise-4.6

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.