You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
How this would happen is unclear.
Ideas (Feedback welcome):
The text was updated successfully, but these errors were encountered: