Skip to content

Hardened ZTWIM GA documentation #429

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
strangiato merged 1 commit into from
Jun 22, 2026
Merged

Hardened ZTWIM GA documentation #429

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
9 changes: 5 additions & 4 deletions zero-trust-workload-identity-manager/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ Do not use the `base` directory directly, as you will need to patch the `channel

The current *overlays* available are for the following channels:

* [stable-v1](operator/overlays/stable-v1)
* [tech-preview](operator/overlays/tech-preview)

### Usage
Expand Down Expand Up @@ -37,22 +38,22 @@ resources:

## Deploy an Instance of Zero Trust Workload Identity Manager

Once the Operator has been installed, an instance of Zero Trust Workload Identity Manager can be deployed. The content is available within the [instance](instance) directory. Similar to the _operator_ deployment described in the prior section, it is not recommended to use the `base` directory, and instead use the contents in the `overlays/default` directory.
Once the Operator has been installed, an instance of Zero Trust Workload Identity Manager can be deployed. The content is available within the [instance](instance) directory. Similar to the _operator_ deployment described in the prior section, it is not recommended to use the `base` directory, and instead use the contents in the `overlays/<channel>>` directory.

### Usage

The default instance enables the configuration of both the `trustDomain`, `jwtIssuer` and `clusterName` fields that are present across multiple Custom Resources associated with the Zero Trust Workload Identity Manager. Update either of these values as desired within the `patches` section of the [kustomization.yaml](instance/overlays/default/kustomization.yaml) file within the `instance/overlays/default` directory.
Cluster specific values for `trustDomain`, `jwtIssuer` and `clusterName` fields that are present across multiple Custom Resources associated with the Zero Trust Workload Identity Manager. Update these values as desired within the `patches` section of the `kustomization.yaml` within the desired _overlay_ directory `instance/overlays/<channel>/kustomization.yaml`.

The instance can be installed by running the following command from the root of the `gitops-catalog` directory.

```
oc apply -k zero-trust-workload-identity-manager/instance/overlays/stable-v1
oc apply -k zero-trust-workload-identity-manager/instance/overlays/<channel>
```

Or, without cloning:

```
oc apply -k https://github.com/redhat-cop/gitops-catalog/zero-trust-workload-identity-manager/instance/overlays/stable-v1
oc apply -k https://github.com/redhat-cop/gitops-catalog/zero-trust-workload-identity-manager/instance/overlays/<channel>
```


Expand Down
3 changes: 3 additions & 0 deletions zero-trust-workload-identity-manager/instance/overlays/stable-v1/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,3 +30,6 @@ patches:
- op: replace
path: /spec/trustDomain
value: 'apps.example.openshift.io'
- op: replace
path: /spec/clusterName
value: 'cluster'