Andreas Lindhé

Thanks for fixing this! Great job! There seem to be some shellcheck warnings left: ```console $ shellcheck bash.sh In bash.sh line 5: pem=$( cat $2 ) # file path of...

It seems like Harbor has prepared support for using an e-mail server to send messages to users, but it is never used. Maybe that could be used for sending vulnerability...

Hey, I just want to say that you are awesome for driving this HIP! 💪 I think there is a dire need for this. I've seen many people loose trust...

> The --timout parameter gets a deeper meaning. > Previously the --timout parameter only had an effect on the helm process running on the respective client. > After implementation, the...

I think this HIP has an additional benefit that should probably be mentioned in the document: it should make multi-user scenarios more robust in general, not just fix the situations...

I think you are on the right track with your implementation, trying to keep this lock inside the Helm release object. That way, we do not introduce new objects to...

> One more thing to discuss that I realized during the implementation: Helm always uses the client time, e..g for the creation of the UPDATED field etc. > > If...

Considering work on Helm 4 has begun, maybe that's what we should target here?

I want to emphasize how important this is. Without resource requests, containers may be scheduled but not get a single second of CPU time to execute. Or get OOMKilled randomly....

I'm also running into issues where the process seems to stop responding but neither the process nor the container get killed. I don't know how to probe this process though…...