#helmfile (2023-12)

https://github.com/helmfile/helmfile

Questions and discussion around helmfile https://github.com/roboll/helmfile and https://github.com/cloudposse/helmfiles

Archive: https://archive.sweetops.com/helmfile/

2023-12-04

SlackBot avatar
SlackBot
02:50:23 PM

This message was deleted.

warrior2031 avatar
warrior2031

Can anyone share working helmfile to deploy basic Scylla cluster?

warrior2031 avatar
warrior2031

I can’t get it working.

$ cat helmfile.yaml
repositories:
◦ name: scylla ```
url: <https://scylla-operator-charts.storage.googleapis.com/stable> ``` ``` releases: ```
◦ name: scylla-operator ```
namespace: scylla
chart: scylla/scylla-operator ```
◦ name: scylla-manager ```
namespace: scylla
chart: scylla/scylla-manager
needs: ```
        • scylla/scylla-operator
◦ name: scylla ```
namespace: scylla
chart: scylla/scylla [I] ~/c/helmfile-playground $ helmfile test Adding repo scylla <https://scylla-operator-charts.storage.googleapis.com/stable> "scylla" has been added to your repositories ``` ``` Testing scylla-operator Testing scylla-manager Testing scylla in ./helmfile.yaml: 3 errors: err 0: release "scylla" failed: command "/opt/local/bin/helm" exited with non-zero status: ``` ``` PATH:   /opt/local/bin/helm ``` ``` ARGS:   0: helm (4 bytes)   1: test (4 bytes)   2: scylla (6 bytes)   3: --namespace (11 bytes)   4: scylla (6 bytes) ``` ``` ERROR:   exit status 1 ``` ``` EXIT STATUS   1 ``` ``` STDERR:   Error: release: not found ``` ``` COMBINED OUTPUT:   Error: release: not found err 1: release "scylla-manager" failed: command "/opt/local/bin/helm" exited with non-zero status: ``` ``` PATH:   /opt/local/bin/helm ``` ``` ARGS:   0: helm (4 bytes)   1: test (4 bytes)   2: scylla-manager (14 bytes)   3: --namespace (11 bytes)   4: scylla (6 bytes) ``` ``` ERROR:   exit status 1 ``` ``` EXIT STATUS   1 ``` ``` STDERR:   Error: release: not found ``` ``` COMBINED OUTPUT:   Error: release: not found err 2: release "scylla-operator" failed: command "/opt/local/bin/helm" exited with non-zero status: ``` ``` PATH:   /opt/local/bin/helm ``` ``` ARGS:   0: helm (4 bytes)   1: test (4 bytes)   2: scylla-operator (15 bytes)   3: --namespace (11 bytes)   4: scylla (6 bytes) ``` ``` ERROR:   exit status 1 ``` ``` EXIT STATUS   1 ``` ``` STDERR:   Error: release: not found ``` ``` COMBINED OUTPUT:   Error: release: not found ```
Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

try to add version for each chart

chart: scylla/scylla-operator
version: xxxxxxx

chart: scylla/scylla-manager
version: xxxxxxx

chart: scylla/scylla
version: xxxxxxx
warrior2031 avatar
warrior2031

No, it results in the same error.

Igor Rodionov avatar
Igor Rodionov

@warrior2031 pls post full helm file. probably there are some intend problem

Tim Birkett avatar
Tim Birkett

@warrior2031 - I know this is 2 weeks oold but the problem is that you are trying to helm test a chart that is not installed….

❯ helm test --help

The test command runs the tests for a release.

The argument this command takes is the name of a deployed release.
The tests to be run are defined in the chart that was installed.

What is it that you are actually trying to achieve by running helmfile test?

Igor Rodionov avatar
Igor Rodionov

@warrior2031 can you pls post helmfile.yaml in single message?

2023-12-05

2023-12-06

Mike Vanbuskirk avatar
Mike Vanbuskirk

Does anyone know how to set a custom log format for an nginx-ingress controller via the terraform helm resource?

andrew.j.gershman avatar
andrew.j.gershman

There are a few ways you can do this. Either the chart has the option for you to pass values that become the body of the custom ConfigMap, or you use the Kubernetes provider to make a ConfigMap with the log format and then pass the name of it to the helm release resource to use for its custom ConfigMap

andrew.j.gershman avatar
andrew.j.gershman

I do believe that mods to the custom ConfigMap are picked up on boot of the ingress controller pods so you may need to kick them with a rolling restart

Mike Vanbuskirk avatar
Mike Vanbuskirk

thanks for responding! I’ve been using those docs, and passing in a values block in the helm resource like so:

values = [
  <<-EOF
  controller:
    config:
      log-format-upstream: '{...}'
  EOF
]
Mike Vanbuskirk avatar
Mike Vanbuskirk

I then roll the pods, but for whatever reason this configuration never actually gets picked up

Mike Vanbuskirk avatar
Mike Vanbuskirk

(this is in GKE)

Mike Vanbuskirk avatar
Mike Vanbuskirk

found the issue

Mike Vanbuskirk avatar
Mike Vanbuskirk

we’re using the bitnami chart, which varies slightly from the k8s one, for reasons…

Mike Vanbuskirk avatar
Mike Vanbuskirk
andrew.j.gershman avatar
andrew.j.gershman

Ah ok. Good times

Mike Vanbuskirk avatar
Mike Vanbuskirk

thank you for replying!

1

2023-12-07

2023-12-20

    keyboard_arrow_up