Raffaele Di Fazio
Raffaele Di Fazio
Isn't this done in #67 ? :-)
@natasha41575 any update on this one? #3446 is hitting us as well.
@christopherhein Sorry for commenting on an existing issue, but you mention here that creating a new resource only takes ~15 mins. Do you have an example/tutorial on how to do...
But that's actually a good one, looking forward for the progress :-)
I'm not entirely sure about the details of this, this is why I add @linki who'll be able to answer clearly. Also, we actually used this with GKE (Container Engine)...
> This is a bit awkward and we should probably allow setting the StatusReader through the Applier/Destroyer builder. I am not familiar with Applier/Destroyer, but we (GitHub) are not using...
@mortent so what you are suggesting is to use https://github.com/kubernetes-sigs/cli-utils/blob/2cd8a3ab4594bddaf7a88ad7c950336867587e12/pkg/kstatus/polling/polling.go#L77 to plug custom status reader for individual resources, right? I have never found this and I indeed agree that it...
/remove-lifecycle stale
Apparently, the AWS CLI will need to take into account the changed behavior, see how the upstream kubernetes issue was closed: https://github.com/kubernetes/kubernetes/issues/88524
@mainred I’m going to take a look at this, I will have to try it on a machine to test it out. Do you think this will also bring performance...