This message was deleted.
# kubernetes
s
This message was deleted.
c
You can always contribute back and make sure it is maintained?
a
Also RabbitMQ provider an Operator now https://github.com/rabbitmq/cluster-operator
j
Bit more of an involved pattern, but I've had lots of luck with using upstream helm charts to be used as upstream templates. And then patching those with Kustomize. That way you can build the layers as needed and all of the changes you make to the upstream are defined in code alongside what was pulled from the upstream. It also means that if there is no Helm chart for a given upstream you can just pull their manifests and use that as your templates. Kustomize also gives you flexibility later to add layers. So if in dev and stage you just want to use your base template with a common patch you can, but you can patch that again in your prod environment to modify it if necessary.