You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @iirekm
Yes, setting up a trains-server on k8s is complex due to the multiple databases, requirements and the external ports that needs to be configured.
I like the idea of switching to Kustomize 👍
How complicated is it to take this docker-compose.yaml and build kustomization YAMLs?
Hi @iirekm
Yes, setting up a trains-server on k8s is complex due to the multiple databases, requirements and the external ports that needs to be configured.
I like the idea of switching to Kustomize 👍
How complicated is it to take this docker-compose.yaml and build kustomization YAMLs?
To support Kustomize you already have almost everything:
run 'helm template' command to remove variable interpolations (Kustomize doesn't need them)
split huge yaml generated by the above commands into smaller (just for ease)
Unfortunately, the Trains chart is far from being any useful. Only a few problems I had with it:
creating storage classes manually - nobody does that, they are provided by k8s (eg to use AWS EBS autoprovisioning)
impossible to reduce PVC size or Elasticsearch CPU requests for development purposes
for HTTP stuff, ingresses are typically used, not zillions of services at separate ports
elasticsearch, mongo, etc - there are existing Helm charts for them which can be included, no need to reinvent the wheel
for many admins, Helm is now passe, long live Kustomize
and many many more...
The text was updated successfully, but these errors were encountered: