[DOCS-13807] k8s enterprise operator installation instructions needs a correction Created: 04/Aug/20 Updated: 29/Oct/23 Resolved: 13/Aug/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Kubernetes Operator |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Jeegar Ghodasara | Assignee: | Melissa Mahoney |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 27 weeks ago |
| Epic Link: | DOCSP-3291 |
| Story Points: | 2 |
| Description |
DescriptionThe Scope of the k8s enterprise operator is cluster-wide, same namespace as resource, or different namespace than resource.
For both cluster-wide scope and different namespace scope, the documentation says operator "MUST be installed with helm" which is not correct.
Link to the doc: https://docs.mongodb.com/kubernetes-operator/v1.6/tutorial/plan-k8s-op-considerations/#k8s-op-short-deployment-scopes Operator in Different Namespace Than ResourcesYou scope the Kubernetes Operator to a namespace. The Kubernetes Operator watches Ops Manager and MongoDB Kubernetes resources in the namespace you specify. You must use helm to install the Kubernetes Operator with this scope. Follow the relevant helm installation instructions, but use the following command to set the namespace for the Kubernetes Operator to watch: Scope of changes
Impact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Melissa Mahoney [ 05/Aug/20 ] |
|
Context from Slack: cian.hatton 1 day ago Jeegar 1 day ago cian.hatton 1 day ago |