OSSMDOC-107 - Migrating ossm from 1.1 to 2.0

[neal-timpe]

This PR addresses the migration procedure from ossm11 to ossm20.

It'll be merged with #26265, which updates the SCMP and configuration documentation, and #26261, which updates the installation procedures.

https://issues.redhat.com/browse/OSSMDOC-107

[openshift-docs-preview-bot]

The preview will be available shortly at:

• https://migrating1120--ocpdocs.netlify.com/

[neal-timpe]

@gbaufake @yxun this is still in progress. I'm still working through the content rob provided. But could you start to review this PR for the migration content? Is there a testing plan for the migration?

[JStickler]

Couple of questions and a couple of small formatting issues.

[gbaufake]

Reviewed last changes from a week ago.

[JStickler]

/cherry-pick enterprise-4.6

[openshift-cherrypick-robot]

@JStickler: new pull request created: #27064

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.

[JStickler]

/cherry-pick enterprise-4.7

[openshift-cherrypick-robot]

@JStickler: #26354 failed to apply on top of branch "enterprise-4.7":

Applying: migrating ossm
.git/rebase-apply/patch:39: trailing whitespace.
You can configure Pilot to schedule or set limits on resource allocation. 
.git/rebase-apply/patch:319: trailing whitespace.
          rootCADir:  /etc/cacerts 
.git/rebase-apply/patch:783: trailing whitespace.
The `ServiceMeshControlPlane` resource has been updated for {ProductName} version 2.0. After you created a v2 version of the `ServiceMeshControlPlane` resource, modify it to take advantage of the new features and to fit your deployment. Consider the following changes to the specification and behavior of {ProductName} 2.0 as you're modifying your `ServiceMeshControlPlane` resource. You can also refer to the {ProductName} 2.0 product documentation for updates to features you use. The v2 resource must be used for {ProductName} 2.0 installations. 
.git/rebase-apply/patch:830: trailing whitespace.
* `spec.origins[x].jwt.triggerRules` specified in the Policy must be mapped into one or more `security.istio.io/v1beta1` AuthorizationPolicy resources. Any `spec.selector.labels` must be configured similarly to the same field on RequestAuthentication.  
.git/rebase-apply/patch:858: trailing whitespace.
Mixer components are disabled by default in version 2.0. If you rely on Mixer plugins for your workload, you must configure your version 2.0 `ServiceMeshControlPlane` to include the Mixer components. 
warning: squelched 26 whitespace errors
warning: 31 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_map.yml
M	modules/ossm-security-mtls.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/ossm-security-mtls.adoc
CONFLICT (content): Merge conflict in modules/ossm-security-mtls.adoc
Auto-merging _topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 migrating ossm
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.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.