helm chart: allow running without GitLab?

[pat-s]

Describe the bug

I am trying to install renku on a k3s cluster. Without GL, Keycloak, Redis. For all of these I'd like to use external/self-hosted components.

While I am able to deselect the sub-charts for Keycloak and Redis, GL configuration still seems to be required.

Error: execution error at (renku/templates/gateway/secret.yaml:5:26): Fill in .Values.gateway.gitlabClientSecret or .Values.global.gateway.gitlabClientSecret with the OIDC client secret you created in Gitlab

In a previous error I also had to define global.gitlabl.registry.host.

Before hitting more errors down this path: is running without GL while using the Helm chart supported? I am aware that since renku v2 GL shouldn't be a hard requirement anymore.

Expected behavior
The helm chart should be able to run without GL configuration.

Run environment (please complete the following information):
chart version v2.9.0

Additional context

Some minor side observations:

• it would be great if Chart.yaml could be updated alongside release so one doesn't need to go to another place to check the latest version.

• requirements.yaml could be integrated into Chart.yaml.

• Helm charts often have their own repo for easier discovery and issue reporting. There are other renku repos with a more specific scope in the org, so maybe moving it to a repo renku-helm would be a good fit?

For reference, here are my current values:

keycloakx:
  enabled: false
redis:
  install: false
postgresql:
  enabled: false
enableV1Services: false
enableInternalGitlab: false
solr:
  enabled: false

global:
  gitlab:
    postgresDatabase: renkudb
    postgresUser: renku
    postgresPassword:
      value: "$REDACTED"
    registry:
      host: "??"
  core:
    versions:
      latest:
        image:
          repository: reg.devxy.io/docker.io/renku/core
  certificates:
    image:
      repository: reg.devxy.io/docker.io/renku/certificates

ui:
  client:
    nodeSelector:
      kubernetes.io/arch: amd64
    image:
      repository: reg.devxy.io/docker.io/renku/renku-ui
  server:
    nodeSelector:
      kubernetes.io/arch: amd64
    image:
      repository: reg.devxy.io/docker.io/renku/renku-ui-server
gateway:
  image:
    repository: reg.devxy.io/docker.io/renku/renku-gateway
jena:
  image:
    repository: reg.devxy.io/docker.io/renku/renku-jena
  persistence:
    size: 5Gi
  resources:
    limits:
      cpu: 3000m
      memory: 2Gi
    requests:
      cpu: 250m
      memory: 500Mi
graph:
  webhookService:
    image:
      repository: reg.devxy.io/docker.io/renku/webhook-service
  tokenRepository:
    image:
      repository: reg.devxy.io/docker.io/renku/token-repository
  triplesGenerator:
    image:
      repository: reg.devxy.io/docker.io/renku/triples-generator
  knowledgeGraph:
    image:
      repository: reg.devxy.io/docker.io/renku/knowledge-graph
  eventLog:
    image:
      repository: reg.devxy.io/docker.io/renku/event-log
  commitEventService:
    image:
      repository: reg.devxy.io/docker.io/renku/commit-event-service
  persistence:
    storageClass: longhorn-retain

swagger:
  image:
    repository: reg.devxy.io/docker.io/swaggerapi/swagger-ui
initDb:
  image:
    repository: reg.devxy.io/docker.io/renku/init-db
platformInit:
  image:
    repository: reg.devxy.io/docker.io/renku/platform-init
dataService:
  nodeSelector:
    kubernetes.io/arch: amd64
  image:
    repository: reg.devxy.io/docker.io/renku/renku-data-service
  k8sWatcher:
    image:
      repository: reg.devxy.io/docker.io/renku/data-service-k8s-watcher
  dataTasks:
    image:
      repository: reg.devxy.io/docker.io/renku/data-service-data-tasks
authz:
  image:
    repository: reg.devxy.io/docker.io/authzed/spicedb
secretsStorage:
  nodeSelector:
    kubernetes.io/arch: amd64
  image:
    repository: reg.devxy.io/docker.io/renku/secrets-storage

notebooks:
  userSessionPersistentVolumes:
    storageClass: longhorn-retain
    size: 5Gi

nodeSelector:
  kubernetes.io/arch: amd64

[olevski]

Hi @pat-s yes we need to fix this.

For the time being you can provide the values that you get errors about. They will not be used and the helm chart should deploy.

Try this. I tried it with helm template ... and it worked. I only added two lines

keycloakx:
  enabled: false
redis:
  install: false
postgresql:
  enabled: false
enableV1Services: false
enableInternalGitlab: false
solr:
  enabled: false
  auth:
    adminUsername: admin # <<<< Added

global:
  gitlab:
    postgresDatabase: renkudb
    postgresUser: renku
    postgresPassword:
      value: "$REDACTED"
    registry:
      host: "??"
  core:
    versions:
      latest:
        image:
          repository: reg.devxy.io/docker.io/renku/core
  certificates:
    image:
      repository: reg.devxy.io/docker.io/renku/certificates
  gateway:
    gitlabClientSecret: not-used  # <<<< Added
ui:
  client:
    nodeSelector:
      kubernetes.io/arch: amd64
    image:
      repository: reg.devxy.io/docker.io/renku/renku-ui
  server:
    nodeSelector:
      kubernetes.io/arch: amd64
    image:
      repository: reg.devxy.io/docker.io/renku/renku-ui-server
gateway:
  image:
    repository: reg.devxy.io/docker.io/renku/renku-gateway
jena:
  image:
    repository: reg.devxy.io/docker.io/renku/renku-jena
  persistence:
    size: 5Gi
  resources:
    limits:
      cpu: 3000m
      memory: 2Gi
    requests:
      cpu: 250m
      memory: 500Mi
graph:
  webhookService:
    image:
      repository: reg.devxy.io/docker.io/renku/webhook-service
  tokenRepository:
    image:
      repository: reg.devxy.io/docker.io/renku/token-repository
  triplesGenerator:
    image:
      repository: reg.devxy.io/docker.io/renku/triples-generator
  knowledgeGraph:
    image:
      repository: reg.devxy.io/docker.io/renku/knowledge-graph
  eventLog:
    image:
      repository: reg.devxy.io/docker.io/renku/event-log
  commitEventService:
    image:
      repository: reg.devxy.io/docker.io/renku/commit-event-service
  persistence:
    storageClass: longhorn-retain

swagger:
  image:
    repository: reg.devxy.io/docker.io/swaggerapi/swagger-ui
initDb:
  image:
    repository: reg.devxy.io/docker.io/renku/init-db
platformInit:
  image:
    repository: reg.devxy.io/docker.io/renku/platform-init
dataService:
  nodeSelector:
    kubernetes.io/arch: amd64
  image:
    repository: reg.devxy.io/docker.io/renku/renku-data-service
  k8sWatcher:
    image:
      repository: reg.devxy.io/docker.io/renku/data-service-k8s-watcher
  dataTasks:
    image:
      repository: reg.devxy.io/docker.io/renku/data-service-data-tasks
authz:
  image:
    repository: reg.devxy.io/docker.io/authzed/spicedb
secretsStorage:
  nodeSelector:
    kubernetes.io/arch: amd64
  image:
    repository: reg.devxy.io/docker.io/renku/secrets-storage

notebooks:
  userSessionPersistentVolumes:
    storageClass: longhorn-retain
    size: 5Gi

nodeSelector:
  kubernetes.io/arch: amd64

[olevski]

I am not sure also if you can truly deploy renku without Solr. The flag is in the values file but I think it is only there in the scenario that you want to deploy solr separately.

[olevski]

it would be great if Chart.yaml could be updated alongside release so one doesn't need to go to another place to check the latest version.

I probably misunderstand what you mean but we publish our helm charts in the helm repo at https://swissdatasciencecenter.github.io/helm-charts.

You should not be using the helm chart from the git repo. The best way is to:

helm repo add renku https://swissdatasciencecenter.github.io/helm-charts
helm repo update renku

Then run something like:

helm upgrade --install -n renku -f values.yaml renku renku/renku

This is mentioned in the docs: https://docs.renkulab.io/en/latest/docs/admins/installation/deployment

[olevski]

Helm charts often have their own repo for easier discovery and issue reporting. There are other renku repos with a more specific scope in the org, so maybe moving it to a repo renku-helm would be a good fit?

I dont think we will do this. As a matter of fact we will combine all the component repos into this repository in the future. Then users do not have to wonder where to open an issue - there will be juts one repo. This will also simplify our development, release and testing process.