Skip to content
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

Cross Cluster Deployments #52

Open
davidmdm opened this issue Jan 5, 2025 · 0 comments
Open

Cross Cluster Deployments #52

davidmdm opened this issue Jan 5, 2025 · 0 comments

Comments

@davidmdm
Copy link
Collaborator

davidmdm commented Jan 5, 2025

Context

Currently the ATC only functions within the cluster it is deployed within.

If a user creates an Airway for "Backends", when backends are created in a namespace, the backend flight implementation is deployed within that namespace.

However it is a common pattern to have "Control" clusters that manage "Workload" clusters.

Ideally via some configuration/mechanism the following would hold true:

  • A user creates an Airway
  • User creates a CR associated to the Airway
  • Package is deployed to a target cluster.

How this would happen is unclear.

Ideas (Feedback welcome):

  • Configure at the Airway Level a mapping from Namespace -> External-Cluster + Namespace.
  • Allow CRs to have special annotations that would deploy them to an external cluster?
  • Other?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant