-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Garbage collector should support non-core APIs #44507
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
Comments
caesarxuchao
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Apr 14, 2017
0xmichalis
added
the
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
label
Apr 14, 2017
lavalamp
added
the
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
label
Apr 22, 2017
@caesarxuchao is this the issue tracking garbage collection for TPR ? |
Same question with @krmayankk This would be really helpful if GC can support TPR :-) |
There is a PR (in progress) with a fix here: #46000. |
Thanks @nikhita |
#47665 is addressing the issue. |
k8s-github-robot
pushed a commit
that referenced
this issue
Jul 29, 2017
Automatic merge from submit-queue (batch tested with PRs 49538, 49708, 47665, 49750, 49528) Enable garbage collection of custom resources Enhance the garbage collector to periodically refresh the resources it monitors (via discovery) to enable custom resource definition GC (addressing #44507 and reverting #47432). This is a replacement for #46000. /cc @lavalamp @deads2k @sttts @caesarxuchao /ref #48065 ```release-note The garbage collector now supports custom APIs added via CustomeResourceDefinition or aggregated apiservers. Note that the garbage collector controller refreshes periodically, so there is a latency between when the API is added and when the garbage collector starts to manage it. ```
Looks like @ironcladlou finished off what I started and this is done. Thanks!! |
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.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
Currently the garbage collector does not handle non-core APIs, like the APIs created via Thirdparty Resource or via the aggregated apiserver.
To support the non-core APIs, Garbage collector needs to:
The text was updated successfully, but these errors were encountered: