Epic Goal

• Define the supported ways to achieve multi tenancy with gitops-operator
  • Apps in any namespace
  • managed-by label

• Publish a blog (Multi tenancy guide)
• Evaluate Aggregated cluster roles against our current approach of creating roles and role bindings in the managed namespaces.

Why is this important?

• Customers look at openshift-gitops as a tool to manage their applications deployment and openshift infrastructure. It is very important to support customers with respect to their use-cases such as
  • managing a single namespaces for one tenant
  • managing multiple namespaces for one tenant
  • managing multiple namespaces for multiple tenants

Scenarios

1. A Customer X who wants to manage their X-dev, X-stage, X-prod using a single openshift-gitops instance.

Acceptance Criteria (Mandatory)

• Publish a multi tenancy blog (to redhat blog) which explains in detail about the options that we provide to achieve multi-tenancy.
• Evaluate GITOPS-2615 - implementation is out of scope.

Dependencies (internal and external)

Previous Work (Optional):

1. ...

Open questions::

1. ...

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment