Skip to content

[enterprise-4.6] OSSMDOC-347: WASM Extensions support is always enabled #38939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 18, 2021
Merged

[enterprise-4.6] OSSMDOC-347: WASM Extensions support is always enabled #38939

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions modules/ossm-extensions-wasm-deploy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,10 @@ spec:
workloadSelector:
labels:
app: httpbin
config: test
image: quay.io/maistra-dev/header-append-filter:2.0
config:
first-header: some-value
another-header: another-value
image: quay.io/maistra-dev/header-append-filter:2.1
phase: PostAuthZ
priority: 100
----
Expand Down
33 changes: 0 additions & 33 deletions modules/ossm-extensions-wasm-support.adoc
View file
Open in desktop

This file was deleted.

6 changes: 2 additions & 4 deletions service_mesh/v2x/ossm-extensions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,7 @@ module: extension.wasm

=== Example Rust extension

For a complete example that was built using the Rust SDK, take a look at the link:https://github.com/maistra/header-append-filter[header-append-filter]. The filter appends a header, called `custom-header`, to all responses, with the value depending on its configuration.

include::modules/ossm-extensions-wasm-support.adoc[leveloffset=+2]
For a complete example that was built using the Rust SDK, take a look at the link:https://github.com/maistra/header-append-filter[header-append-filter]. It is a simple filter that appends one or more headers to the HTTP responses, with their names and values taken out from the `config` field of the extension. See a sample configuration in the snippet below.

include::modules/ossm-extensions-wasm-deploy.adoc[leveloffset=+2]

Expand All @@ -108,7 +106,7 @@ include::modules/ossm-extensions-wasm-deploy.adoc[leveloffset=+2]
|The `spec.workloadSelector` field has the same semantic as the `spec.selector` field of the link:https://istio.io/v1.6/docs/reference/config/networking/gateway/#Gateway[Istio Gateway resource]. It will match a workload based on its Pod labels. If no `workloadSelector` is specified, the extension will be applied to all workloads in the namespace.

|spec.config
|This is a pass-through string field that is handed over to the extension. Syntax and semantics are dependent on the extension that you are deploying.
|This is a structured field that will be handed over to the extension, with the semantics dependent on the extension you are deploying.

|spec.image
|A container image URI pointing to the image that holds the extension.
Expand Down