Skip to content
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

Jump to bottom

Adds provision in Integration config docs #80

Merged
merged 2 commits into from
Dec 8, 2023
Merged

Adds provision in Integration config docs #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b09da73
adds provision
SheryarButt Dec 8, 2023
3c6ea74
updates in IC doc and uninstallation
SheryarButt Dec 8, 2023
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
4 changes: 4 additions & 0 deletions content/how-to-guides/offboarding/uninstalling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,10 @@ You can uninstall MTO by following these steps:

* Decide on whether you want to retain tenant namespaces and ArgoCD AppProjects or not. If yes, please set `spec.onDelete.cleanNamespaces` to `false` for all those tenants whose namespaces you want to retain, and `spec.onDelete.cleanAppProject` to `false` for all those tenants whose AppProject you want to retain. For more details check out [onDelete](../../tutorials/tenant/deleting-tenant.md#retaining-tenant-namespaces-and-appproject-when-a-tenant-is-being-deleted)

* In case you have enabled console, you will have to disable it first by navigating to `Search` -> `IntegrationConfig` -> `tenant-operator-config` and set `spec.provision.console` and `spec.provision.showback` to `false`.

* Remove IntegrationConfig CR from the cluster by navigating to `Search` -> `IntegrationConfig` -> `tenant-operator-config` and select `Delete` from actions dropdown.

* After making the required changes open OpenShift console and click on `Operators`, followed by `Installed Operators` from the side menu

![image](../../images/installed-operators.png)
Expand Down
24 changes: 24 additions & 0 deletions content/integration-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,9 @@ spec:
sso:
clientName: vault
accessorID: <ACCESSOR_ID_TOKEN>
provision:
console: true
showback: true
```

Following are the different components that can be used to configure multi-tenancy in a cluster via Multi Tenant Operator.
Expand Down Expand Up @@ -371,3 +374,24 @@ If enabled, than admins have to provide secret, URL and SSO accessorID of Vault.
- `sso.clientName:` Will contain the client name.

For more details please refer [use-cases](./usecases/integrationconfig.md)

## Provision

```yaml
provision:
console: true
showback: true
```

`provision.console:` Can be used to enable/disable console GUI for MTO.
`provision.showback:` Can be used to enable/disable showback feature on the console.

Integration config will be managing the following resources required for console GUI:

- `Showback` cronjob.
- `Keycloak` deployment.
- `MTO-OpenCost` operator.
- `MTO-Prometheus` operator.
- `MTO-Postgresql` stateful set.

Details on console GUI and showback can be found [here](explanation/console.md)
Loading