Fixes

• Allow the possibility to specify CELERY_CONFIG_MODULE. Fix #8 (closed)
• flower and flask use ClusterIP service
• embright concurrency reduced to 1 to decrease memory footprint of ~1Gi
• Deploy containers.ligo.org/emfollow/gwcelery:v2.6.0
• Redis changed to ClusterIP service

mentioned in merge request !11 (closed)

Various changes for improving LDAS k3s deployment

• flower and flask use ClusterIP service
• embright concurrency reduced to 1 to decrease memory footprint of ~1Gi
• Define gwcelery.conf to specify the existing configuration to be used
• Deploy deploy V.2.6.0 instead of main

added 1 commit

• 7aa325ff - Use CluserIP instead of NodePort for flower/falsk. embright concurency=1, deploy V.2.6.0

Compare with previous version

mentioned in issue #8 (closed)

assigned to @roberto.depietri

requested review from @sara.vallero

changed the description

For clarity, I would rename conf in celeryCongifFile or celeryConfigModule. If I specify a custom name, is there a logic that creates a configmap from that file and mounts it in the right directory?

Using a custom name means we may specify a different configuration (e.g., dev, playground, prod, test) instead of minikube. No need to mount in the right directory. The config map is there to use a provided config and run it using helm-k8s as name 'gwcelery.conf.helm-k8s'

Ok, I see.

added 1 commit

• 9a506852 - Change value gwcelery.conf=>celeryConfigModule

Compare with previous version

added 2 commits

• 2431becc - 1 commit from branch emfollow/k8s:main
• 8a22b8c7 - Merge branch helm:main into fixes

Compare with previous version

added 4 commits

• f665235e - Allow to specity configuration setting for gwcelery
• d8c7c9ad - Allow to specity configuration setting for gwcelery
• d000c1f6 - Use CluserIP instead of NodePort for flower/falsk. embright concurency=1, deploy V.2.6.0
• b69f987c - Change value gwcelery.conf=>celeryConfigModule

Compare with previous version

added 1 commit

• 0680d811 - Set redis master.service.type=ClusterIP since Redis is deployed possworless

Compare with previous version

changed the description

@sara.vallero Deployed on fluxuser2:

helm  upgrade --install  gwcelery  ./gwcelery/  --set gwcelery.storageClassName=local-path --set gwcelery.ingress.host=fluxuser2.ldas.cit --set gwcelery.gracedb.hostname=gracedb-dev2.ldas.cit`

This FIX possible vulnerability of the exposed services (That would create vulnerability detection false positive on machines that are exposed to the internet)

Yes, in general I would use LoadBalancer only for Traefik because on a self-contained distribution like k3s or minikube one can easily have conflicts (typically only 1 IP available).

Even more generally, it's up to the user NOT to expose stuff that is not TLS to the public, we should add a note in the docs for hybrid deployments (in preparation).

approved this merge request

It can be merged and tagged according to me.

added 1 commit

• 03fe6572 - Update Chart and app version to 1.0.3 and v2.6.0

Compare with previous version

reset approvals from @sara.vallero by pushing to the branch

added 1 commit

• 818508f7 - Allow to specity configuration setting for gwcelery

Compare with previous version

merged