Lili Cosic
Lili Cosic
@dlespiau I would suggest to export the `waitForDeploymentReady` and convert that to `WaitForDeploymentReadyByName((ns, name, duration)` that way there is both options. WDYT? https://github.com/dlespiau/kube-harness/blob/ce8cb74e61fe701580166e37bb6b95e8cc431729/deployment.go#L72
@x13n Thanks for your reply! I think that solves the configuration aspect, and that would work for our setup. But the configmap status would still be created in the other...
Yes the point was to help out the release manager, that does not mean it will be an automated process, but it will certainly help with the CHANGELOG text msg...
So we seem to have an agreement or no one is really opposed to this? Anyone want to take this on?
/remove-lifecycle rotten Personally, still think we should move away from it :)
I agreed, with @brancz approach, but I believe a lot of people already heavily use this, so I would prefer to add a new field if its causing this much...
Hey, @dashpole 👋 I am always on board when it comes to adding more observability signals into any project and tracing is something that is very useful! With that being...
@dashpole Thank you for that! I think the value of having one trace context propagated from apiserver to etcd would be amazing for insight! But code freeze is mid-May for...
@logicalhan makes sense thank you for that yes! > Following-up from the earlier comment, there isn't a fixed-size buffer. It looks like this is a case where we will just...
cc @simonpasquier we already had a chat about this.