Merge upstream/3.5.1

[srvaroa]

• Kafka manager with web UI to monitor and maintain Kafka's clusters
• configured max-old-space-size for js-executor
• typo
• added max-old-space-size for web-ui
• Version set to 3.4.2
• Version set to 3.4.3
• add tb-edge-loadbalancer
• fix http transport bind port for load-balancer
• Delete the TRANSPORT_TYPE variable as unused
• Added upgrade launch script
• Release 3.4.4
• Version set to 3.5.0
• gcp edge load balancer for monolith
• Added AWS and Azure Edge load balancer receipts
• Increase Kafka logs volume size to 10Gi
• Version set to 3.5.1

[xavileon]

nice, we only use helm though, so most of the updates will remain unused.

[xavileon]

on second thought, we diverted so much from upstream, that maybe it's better to remove all directories except helm to clean up what is not really used?

[srvaroa]

I am kind of sympathetic to removing the unused stuff, BUT, that means we automatically force us to a hard-fork of the chart, and keeping things up to date will be a lot harder.

It seems simpler to me to just be disciplined keeping our fork up to date with upstream. If there are updates that are not relevant to us that's harmless. But we ensure that we remain aligned with upstream releases.

[maht]

I am kind of sympathetic to removing the unused stuff, BUT, that means we automatically force us to a hard-fork of the chart, and keeping things up to date will be a lot harder.

It seems simpler to me to just be disciplined keeping our fork up to date with upstream. If there are updates that are not relevant to us that's harmless. But we ensure that we remain aligned with upstream releases.

At the beginning I agreed in thinking it was easier to just maintain it, but I think we should somehow put a disclaimer in the README about the fact that Midokura changes are only tested with Helm, and the other providers are probably not updated and/or usable.

Otherwise a newcomer could spent to much time before realize that they are basically broken and we only kept them to make sync with upstream easier.

[srvaroa]

I don't think that the default reasonable assumption from a random internet person that finds this fork is that we're actually supporting the whole thing, but random internet people is not famous for being reasonable, so yes, a disclaimer might be a good idea!

[xavileon]

It seems simpler to me to just be disciplined keeping our fork up to date with upstream. If there are updates that are not relevant to us that's harmless. But we ensure that we remain aligned with upstream releases.

Sounds reasonable! Let's look in EVP how to be disciplined in keeping this fork up to date 👍