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.

Sign up for GitHub

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

Jump to bottom

filtering resources when import cluster #142

Open
sanposhiho opened this issue Apr 13, 2022 · 6 comments
Open

filtering resources when import cluster #142

sanposhiho opened this issue Apr 13, 2022 · 6 comments
Labels
area/simulator Issues or PRs related to the simulator. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@sanposhiho
Copy link
Member

Idea from #141
Currently when we import resources on existing clusters, we try to import all resources on that cluster.

It would be nice to be able to define filters to determine which resources to import.

/kind feature
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 13, 2022
@sanposhiho sanposhiho mentioned this issue Apr 24, 2022
Merged
@sanposhiho
Copy link
Member Author

/triage accepted
Not to mark as stale.

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Jun 7, 2022
@sanposhiho
Copy link
Member Author

/area simulator

@k8s-ci-robot k8s-ci-robot added the area/simulator Issues or PRs related to the simulator. label Sep 4, 2022
@26tanishabanik
Copy link

@sanposhiho , can you provide more details on this issue?

@sanposhiho
Copy link
Member Author

I'd say we can introduce labelSelector and namespaceSelector to judge which resources should be imported.

@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 19, 2024
@sanposhiho
Copy link
Member Author

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/simulator Issues or PRs related to the simulator. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@k8s-ci-robot @sanposhiho @26tanishabanik @k8s-triage-robot