diff options
author | Patrick Jahns <kontakt@patrickjahns.de> | 2022-11-16 12:18:11 +0100 |
---|---|---|
committer | Gitea <gitea@fake.local> | 2022-12-11 23:11:56 +0000 |
commit | f58a813a36de7b356d72ba1e6f2f991da5491285 (patch) | |
tree | 9ce275519554c2cedf18b3034e24babc8bf21ef2 | |
parent | defd7d9e6353e10b0b9d58b66aad4f04e7d50c41 (diff) | |
download | garage-f58a813a36de7b356d72ba1e6f2f991da5491285.tar.gz garage-f58a813a36de7b356d72ba1e6f2f991da5491285.zip |
refactor(helm): disable the ingress per default
The default values forces people to create an ingress resources,
where per default an ingress is not necessary to start garage.
If someone wants to utilize an ingress, he would need to define
the values for the ingress either way, so enabling the ingress
explicitly makes more sense, then requiring it to be disabled per default
-rw-r--r-- | script/helm/garage/values.yaml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/script/helm/garage/values.yaml b/script/helm/garage/values.yaml index 08d0c09b..9c1c54c0 100644 --- a/script/helm/garage/values.yaml +++ b/script/helm/garage/values.yaml @@ -85,12 +85,12 @@ service: ingress: s3: api: - enabled: true + enabled: false # Rely either on the className or the annotation below but not both # replace "nginx" by an Ingress controller # you can find examples here https://kubernetes.io/docs/concepts/services-networking/ingress-controllers - className: "nginx" - annotations: + # className: "nginx" + annotations: {} # kubernetes.io/ingress.class: "nginx" # kubernetes.io/tls-acme: "true" hosts: @@ -107,8 +107,11 @@ ingress: # hosts: # - kubernetes.docker.internal web: - enabled: true - className: "nginx" + enabled: false + # Rely either on the className or the annotation below but not both + # replace "nginx" by an Ingress controller + # you can find examples here https://kubernetes.io/docs/concepts/services-networking/ingress-controllers + # className: "nginx" annotations: {} # kubernetes.io/ingress.class: nginx # kubernetes.io/tls-acme: "true" |