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

Refactor 'destination' configuration for consistency across Backup and Application #439

Open
Xieql opened this issue Nov 8, 2023 · 2 comments
Assignees

Comments

@Xieql
Copy link
Contributor

Xieql commented Nov 8, 2023

What would you like to be added:
Refactor 'destination' configuration for consistency across Backup and Application

Why is this needed:
In our current implementation, we have a destination configuration that behaves differently in Backup and Application. In Backup, it allows specifying a cluster, while in scenario Application, it allows targeting a group of clusters with a specific label.

This discrepancy can lead to user confusion as the goal is the same—to designate a target destination cluster for a task—but the method differs.

To address this, I propose we refactor the 'destination' configuration to support both settings methods—specifying a single cluster or a group of clusters with a tag—in both Backup and Application.

@Xieql Xieql changed the title Refactor 'destination' configuration for consistency across Fleet and Application Refactor 'destination' configuration for consistency across Backup and Application Nov 8, 2023
@hzxuzhonghu
Copy link
Member

What do you think and how we can better design the target clusters

@Xieql
Copy link
Contributor Author

Xieql commented Nov 18, 2023

What do you think and how we can better design the target clusters

I think we can support both settings methods in any crd

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

2 participants