Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13807

k8s enterprise operator installation instructions needs a correction

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Kubernetes Operator
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Epic Link:
    • Sprint:
      CET: Andromeda (4-10 Aug 2020), CET: Betelgeuse (8/11 - 8/17)

      Description

      Description

      The 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 Resources

      You 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

      • Remove "must"
      • Include that helm is preferred
      • Point to/note on how to do it without helm

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Activity

            People

            Assignee:
            melissa.mahoney Melissa Mahoney
            Reporter:
            jeegar.ghodasara Jeegar Ghodasara
            Participants:
            Last commenter:
            Melissa Mahoney Melissa Mahoney
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              1 year, 16 weeks, 4 days ago
              Date of 1st Reply: