search

zalf-rdm / geonode-k8s

A Kubernetes helm chart for the geospacial webapplication Geonode
https://geonode-k8s.readthedocs.io/en/latest/
GNU General Public License v2.0
12 stars 7 forks source link

Task: Use release name in all K8s resource names #120

Closed AlexGacon closed 7 months ago

AlexGacon commented 7 months ago

Task Description

Some resources don't have a name which includes the release name, making it difficult to find all the K8s resources related to a given deployment

Additional Information

at least, there are geonode-secret and geoserver-secret.

ridoo commented 7 months ago

Perhaps this is a personal view and there may be reasons against it, but why not deploying everything in a dedicated namespace, e.g. using Helm's --namespace flag. IMO we could get rid of all "release pod name" helper functions.

/cc @mwallschlaeger

AlexGacon commented 7 months ago

If you go this way, you put hard requirements on how you organize the K8s cluster : you must use namespaces to organize your cluster, you cannot have several geonode deployments in the same namespace (for example, several customers with different settings in a namespace dev).

mwallschlaeger commented 7 months ago

yes @AlexGacon i agree to you. one helm Chart deployment should end up in a single namespace. and tighten together all objects of a deployment with a prefix to the name of the objects is common patten. therefore i would agree on giving all objects the release name as prefix.