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, when an Argo CD Application is created on a spoke cluster, there is no default behavior for setting the destination.server field to https://kubernetes.default.svc.
I propose adding a default behavior where the destination.server is automatically set to https://kubernetes.default.svc.
Additionally, an option should be provided to disable this defaulting behavior to enable more flexible deployment scenarios. Such as the fan-out model.
Reason:
The pull model is primarily designed for spoke clusters to reconcile their own state and perform in-cluster processing independently. When the destination.server is not explicitly set to the https://kubernetes.default.svc, it introduces the possibility of users picking any destinations. This can lead to inconsistencies and management complexity.
However, for experts and complex scenarios, this option should still be available. So a configuration should be provided to disable the default behavior (or enable the fan-out mode) as needed.
The text was updated successfully, but these errors were encountered:
Currently, when an Argo CD Application is created on a spoke cluster, there is no default behavior for setting the destination.server field to
https://kubernetes.default.svc
.I propose adding a default behavior where the destination.server is automatically set to
https://kubernetes.default.svc
.Additionally, an option should be provided to disable this defaulting behavior to enable more flexible deployment scenarios. Such as the fan-out model.
Reason:
The pull model is primarily designed for spoke clusters to reconcile their own state and perform in-cluster processing independently. When the destination.server is not explicitly set to the
https://kubernetes.default.svc
, it introduces the possibility of users picking any destinations. This can lead to inconsistencies and management complexity.However, for experts and complex scenarios, this option should still be available. So a configuration should be provided to disable the default behavior (or enable the fan-out mode) as needed.
The text was updated successfully, but these errors were encountered: