only deploy runtime nodes

[bokristoffersson]

When running in production we are investigating in running without an admin server since no configuration changes are to be made outside of gitops configuration.

[anestos]

Isn't a better approach to not deploy anything related to admin when curity.onlyRuntimeNodes is set to true?
you can have an {{- if not .Values.curity.onlyRuntimes -}} at the top of the deployment-admin and service-admin.

Similarly, the backup, cluster-conf job and related resources are not necessary, since there is no connection between the runtime nodes and also there is no interface for confiugration changes to trigger a backup.

finally, the ingress resource should also if enabled, not configure a route for the admin, if onlyRuntimes is true

[bokristoffersson]

True. That make sense.

[bokristoffersson]

I put this into draft. I question if it is a good idea to have this in the charts? It will add some complexity and maybe it is not needed at all. If you want to deploy only runtime nodes you might as well use the manifest files anyway since it will be only deployment, service and ingress. Thus, If it will not be used there is no need for it.

[bokristoffersson]

I opened this again. Since we are able to now convert keystores during startup it really make sense to also be able to use the Helm charts for production using only runtime nodes. I also implemented your suggestion above and now Helm will only create manifest files that are needed.

[bokristoffersson]

Sorry. I deleted the branch unintentionally.

[anestos]

This PR needs a little bit more love @bokristoffersson .
using {{- if eq .Values.curity.onlyRuntimeNodes false }} can be problematic for users of the helm chart that don't have that setting in their values file. Can you negate it? Either {{- if not .Values.curity.onlyRuntimes -}} or {{- if ne .Values.curity.onlyRuntimeNodes true }}`.

Also can you document the curity.onlyRuntimeNodes setting in the readme ?

[anestos]

Will be solved when #114 is merged