Manage applications in multiple environments on separate Kubernetes clusters

[rynowak]

Overview of feature request

Radius should be able to manage applications across environments that are not on the same Kubernetes cluster as the control plane.

Examples:

• Radius is installed in Kubernetes cluster control-plane. It can manage applications on Kubernetes clusters prod-westus and prod-eu-2 using environments that target those clusters (env-prod-westus, env-prod-eu-2).
• Radius is running on a VM. It can manage applications on Kubernetes clusters prod-westus and prod-eu-2 using environments that target those clusters (env-prod-westus, env-prod-eu-2).

Out of scope: Defining an environment that spans multiple compute clusters. Each environment will map to a single Kubernetes cluster. A Kubernetes cluster can still contain multiple environments.

Acceptance criteria

• Decouple Radius from the Kubernetes cluster where applications are running.
• Define environments in a way that identifies and holds credentials for a specific Kubernetes cluster.
• Manage applications on (potentially multiple) Kubernetes clusters. Use the environment to select the destination.

AB#10707

[radius-triage-bot[bot]]

:wave: @rynowak Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[radius-triage-bot[bot]]

:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview