OSSMDOC-550: Document new WasmPlugin API.

[JStickler]

OSSMDOC-550: Document new WasmPlugin API.

OCP versions 4.6 - 4.11

This PR:

• Breaks the existing extensions assembly into ServiceMeshExtension modules
• Adds modules for the new WasmPlugin extension

Link to final docs preview: http://file.bos.redhat.com/jstickle/OSSMDOC-550/service_mesh/v2x/ossm-extensions.html

Link to docs preview: https://deploy-preview-45111--osdocs.netlify.app/openshift-enterprise/latest/service_mesh/v2x/ossm-extensions

Eng review - dgn, jwendell
QE review - skondkar
Peer review - jldohmann

[netlify]

✅ Deploy Preview for osdocs ready!

Name	Link
🔨 Latest commit	ad5b853bf7a85e3b0ad5474c441f1bbf15b05273
🔍 Latest deploy log	https://app.netlify.com/sites/osdocs/deploys/6282a9d105afa10008ff31c1
😎 Deploy Preview	https://deploy-preview-45111--osdocs.netlify.app/openshift-enterprise/latest/service_mesh/v2x/ossm-extensions
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[JStickler]

@dgn, please review since you are the resident expert on WASM.

[dgn]

lgtm except for the container image format

[JStickler]

@dgn I revised the WasmPlugin container format topic. I could use a second review for that topic please.

[skondkar]

Verified with the steps in preview doc. Created WasmPlugin for OSSM 2.2

When creating ServiceMeshExtenstion on 2.2, got the error for unrecognized type ServiceMeshExtension
Successfully created ServiceMeshExtenstion on 2.1 as per the example in the preview doc

[jwendell]

@skondkar Can you provide more details on the error on 2.2? Feel free to create a ticket in Jira with the details/step to reproduce and tag me there.

[skondkar]

About error on 2.2, the steps followed:

• I referred to the section (Deploying ServiceMeshExtension resources) - https://deploy-preview-45111--osdocs.netlify.app/openshift-enterprise/latest/service_mesh/v2x/ossm-extensions#ossm-smextensions-deploy_ossm-extensions

• Created V2.2 SMCP, then I tried to apply below yaml file:

apiVersion: maistra.io/v1
kind: ServiceMeshExtension
metadata:
name: header-append
namespace: istio-system
spec:
workloadSelector:
labels:
app: httpbin
config:
first-header: some-value
another-header: another-value
image: quay.io/maistra-dev/header-append-filter:2.1
phase: PostAuthZ
priority: 100

• It shows below error after applying the file:

Error from server: error when creating "extension.yaml": admission webhook "rev.validation.istio.io" denied the request: unrecognized type ServiceMeshExtension

• It works if i install v2.1 SMCP and apply the same yaml file

[jwendell]

Please, create a Jira and include all details in there (OCP version, SMCP yaml, etc)

[skondkar]

@jwendell thanks,
Created the issue to track: https://issues.redhat.com/browse/OSSM-1597

[skondkar]

LGTM.
Tested the PR again after verifying issue [OSSM-1597] on OSSM 2.2 latest build.
Created WasmPlugin resources and ServiceMeshExtension resource successfully on SMCP v2.2 as per the preview doc.

Verified that while creating ServiceMeshExtension, it shows below warning:
Warning: ServiceMeshExtension is deprecated. It works now but will be removed in a future version. Please use WasmPlugin instead.

[JStickler]

@jwendell @skondkar if I'm reading the comments on this correctly, now that we have a user friendly message about the ServiceMeshExtension, am I good to move this PR to peer review? Or is there something else I need to update?

[JStickler]

Received ack via Slack that this PR is good to go and can move to peer review.

[jldohmann]

Looking good! Mostly some minor ISG nits and API object references. I realize that a lot of what GH perceives as file changes in content are actually from modularization, so if any of this is out of scope with your changes, I apologize

[JStickler]

Added note that WebAssembly extensions not supported on IBM Power and Z systems at request of IBM technical writers.

[JStickler]

Merging now to get this into main so that Eng and 3scale team can work on documenting the next steps.

[JStickler]

/cherry-pick enterprise-4.6

[JStickler]

/cherry-pick enterprise-4.7

[JStickler]

/cherry-pick enterprise-4.8

[JStickler]

/cherry-pick enterprise-4.9

[JStickler]

/cherry-pick enterprise-4.10

[JStickler]

/cherry-pick enterprise-4.11

[openshift-cherrypick-robot]

@JStickler: new pull request created: #47251

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.

[openshift-cherrypick-robot]

@JStickler: new pull request created: #47252

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.

[openshift-cherrypick-robot]

@JStickler: new pull request created: #47253

In response to this:

/cherry-pick enterprise-4.9

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.

[openshift-cherrypick-robot]

@JStickler: new pull request created: #47254

In response to this:

/cherry-pick enterprise-4.10

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.

[openshift-cherrypick-robot]

@JStickler: new pull request created: #47255

In response to this:

/cherry-pick enterprise-4.11

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.8

[openshift-cherrypick-robot]

@JStickler: new pull request created: #47256

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.