-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Updates installation guide #78
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,7 +10,7 @@ | |
|
||
## Requirements | ||
|
||
* An **OpenShift** cluster [v4.7 - v4.12] | ||
* An **OpenShift** cluster [v4.8 - v4.13] | ||
|
||
## Installing via OperatorHub UI | ||
|
||
|
@@ -42,34 +42,6 @@ | |
|
||
> Note: MTO will be installed in `multi-tenant-operator` namespace. | ||
|
||
### Configuring IntegrationConfig | ||
|
||
IntegrationConfig is required to configure the settings of multi-tenancy for MTO. | ||
|
||
* We recommend using the following IntegrationConfig as a starting point | ||
|
||
```yaml | ||
apiVersion: tenantoperator.stakater.com/v1alpha1 | ||
kind: IntegrationConfig | ||
metadata: | ||
name: tenant-operator-config | ||
namespace: multi-tenant-operator | ||
spec: | ||
openshift: | ||
privilegedNamespaces: | ||
- default | ||
- ^openshift-* | ||
- ^kube-* | ||
- ^redhat-* | ||
privilegedServiceAccounts: | ||
- ^system:serviceaccount:default-* | ||
- ^system:serviceaccount:openshift-* | ||
- ^system:serviceaccount:kube-* | ||
- ^system:serviceaccount:redhat-* | ||
``` | ||
|
||
For more details and configurations check out [IntegrationConfig](./integration-config.md). | ||
|
||
## Installing via CLI OR GitOps | ||
|
||
* Create namespace `multi-tenant-operator` | ||
|
@@ -107,11 +79,7 @@ | |
name: tenant-operator | ||
source: certified-operators | ||
sourceNamespace: openshift-marketplace | ||
startingCSV: tenant-operator.v0.9.1 | ||
config: | ||
env: | ||
- name: ENABLE_CONSOLE | ||
value: 'true' | ||
startingCSV: tenant-operator.v0.10.0 | ||
EOF | ||
subscription.operators.coreos.com/tenant-operator created | ||
``` | ||
|
@@ -134,33 +102,40 @@ | |
|
||
![image](./images/to_installed_successful_pod.png) | ||
|
||
### Configuring IntegrationConfig | ||
For more details and configurations check out [IntegrationConfig](./integration-config.md). | ||
|
||
IntegrationConfig is required to configure the settings of multi-tenancy for MTO. | ||
## Enabling Console | ||
|
||
* We recommend using the following IntegrationConfig as a starting point: | ||
To enable console gui for MTO, go to `Search` -> `IntegrationConfig` -> `tenant-operator-config` and make sure the following fields are set to `true`: | ||
Check failure on line 109 in content/installation.md
|
||
|
||
```yaml | ||
apiVersion: tenantoperator.stakater.com/v1alpha1 | ||
kind: IntegrationConfig | ||
metadata: | ||
name: tenant-operator-config | ||
namespace: multi-tenant-operator | ||
spec: | ||
openshift: | ||
privilegedNamespaces: | ||
- default | ||
- ^openshift-* | ||
- ^kube-* | ||
- ^redhat-* | ||
privilegedServiceAccounts: | ||
- ^system:serviceaccount:default-* | ||
- ^system:serviceaccount:openshift-* | ||
- ^system:serviceaccount:kube-* | ||
- ^system:serviceaccount:redhat-* | ||
provision: | ||
console: true | ||
showback: true | ||
``` | ||
|
||
For more details and configurations check out [IntegrationConfig](./integration-config.md). | ||
> Note: If your install plan approval is set to `Manual` then you will have to manually approve the install plan for MTO console components to be installed. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [LanguageTool] reported by reviewdog 🐶 |
||
|
||
### Manual Approval | ||
|
||
* Open OpenShift console and click on `Operators`, followed by `Installed Operators` from the side menu. | ||
|
||
![image](./images/manual-approve-1.png) | ||
|
||
* Now click on `Upgrade available` in front of `mto-opencost` or `mto-prometheus`. | ||
|
||
![image](./images/manual-approve-2.png) | ||
|
||
* Now click on `Preview InstallPlan` on top. | ||
|
||
![image](./images/manual-approve-3.png) | ||
|
||
* Now click on `Approve` button. | ||
|
||
![image](./images/manual-approve-4.png) | ||
|
||
* Now the install plan will be approved and MTO console components will be installed. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [LanguageTool] reported by reviewdog 🐶 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [LanguageTool] reported by reviewdog 🐶 |
||
|
||
## Uninstall via OperatorHub UI | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[LanguageTool] reported by reviewdog 🐶
The word ‘install’ is not a noun. (A_INSTALL[1])
Suggestions:
installation
Rule: https://community.languagetool.org/rule/show/A_INSTALL?lang=en-US&subId=1
Category: GRAMMAR