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

[ClusterResourceSet] Add Sync mode #3447

Closed
sedefsavas opened this issue Aug 3, 2020 · 10 comments
Closed

[ClusterResourceSet] Add Sync mode #3447

sedefsavas opened this issue Aug 3, 2020 · 10 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@sedefsavas
Copy link

sedefsavas commented Aug 3, 2020

User Story

As a developer/user/operator I would like to apply a resource using ClusterResourceSet and update its version or change some other fields using the same ClusterResourceSet resource.

Detailed Description

To support this use case, we can consider adding a Sync/Reconcile mode in addition to ApplyOnce mode that reapplies the resources on resource hash change and/or periodically.

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 3, 2020
@vincepri
Copy link
Member

vincepri commented Aug 3, 2020

/milestone v0.4.0

@k8s-ci-robot k8s-ci-robot added this to the v0.4.0 milestone Aug 3, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2020
@vincepri
Copy link
Member

vincepri commented Nov 2, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2020
@vincepri
Copy link
Member

vincepri commented Nov 2, 2020

/milestone Next

@k8s-ci-robot k8s-ci-robot modified the milestones: v0.4.0, Next Nov 2, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 31, 2021
@vincepri
Copy link
Member

vincepri commented Feb 1, 2021

@sedefsavas Are we still interested in pushing this forward or should we close it for now?

@sedefsavas
Copy link
Author

There were no requests to move this forward, I think we can close it until there are new use cases.

@jessehu
Copy link
Contributor

jessehu commented Jan 9, 2023

Hi gurus, can we reopen this please? We have a upgrade case that need to re-apply this CRS (with updated secret content). Thanks.

@sbueringer
Copy link
Member

@jessehu I think this issue was essentially superceded by: #4807 Can you please check if the new issue fulfills your use case?

@jessehu
Copy link
Contributor

jessehu commented Jan 9, 2023

Exactly! Glad to see it's almost done 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants