#helmfile (2023-12)
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](https://slack.global.ssl.fastly.net/66f9/img/slackbot_32.png)
This message was deleted.
![warrior2031 avatar](https://secure.gravatar.com/avatar/5f06068bb9b4c00f12582ccc0ba64c4a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0006-72.png)
Can anyone share working helmfile to deploy basic Scylla cluster?
![warrior2031 avatar](https://secure.gravatar.com/avatar/5f06068bb9b4c00f12582ccc0ba64c4a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0006-72.png)
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](https://avatars.slack-edge.com/2018-06-13/382332470551_54ed1a5d986e2068fd9c_72.jpg)
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](https://secure.gravatar.com/avatar/5f06068bb9b4c00f12582ccc0ba64c4a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0006-72.png)
No, it results in the same error.
![Igor Rodionov avatar](https://secure.gravatar.com/avatar/bc70834d32ed4517568a1feb0b9be7e2.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0015-72.png)
@warrior2031 pls post full helm file. probably there are some intend problem
![Tim Birkett avatar](https://avatars.slack-edge.com/2022-11-30/4444729747651_15dbd309e75baf969dbe_72.png)
@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](https://secure.gravatar.com/avatar/bc70834d32ed4517568a1feb0b9be7e2.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0015-72.png)
@warrior2031 can you pls post helmfile.yaml
in single message?
2023-12-05
2023-12-06
![Mike Vanbuskirk avatar](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
Does anyone know how to set a custom log format for an nginx-ingress controller via the terraform helm resource?
![andrew.j.gershman avatar](https://secure.gravatar.com/avatar/418b335076da0f7b2a2e488f55dd56bf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0018-72.png)
![andrew.j.gershman avatar](https://secure.gravatar.com/avatar/418b335076da0f7b2a2e488f55dd56bf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0018-72.png)
![andrew.j.gershman avatar](https://secure.gravatar.com/avatar/418b335076da0f7b2a2e488f55dd56bf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0018-72.png)
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](https://secure.gravatar.com/avatar/418b335076da0f7b2a2e488f55dd56bf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0018-72.png)
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](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
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](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
I then roll the pods, but for whatever reason this configuration never actually gets picked up
![Mike Vanbuskirk avatar](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
(this is in GKE)
![Mike Vanbuskirk avatar](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
found the issue
![Mike Vanbuskirk avatar](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
we’re using the bitnami chart, which varies slightly from the k8s one, for reasons…
![Mike Vanbuskirk avatar](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)
![andrew.j.gershman avatar](https://secure.gravatar.com/avatar/418b335076da0f7b2a2e488f55dd56bf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0018-72.png)
Ah ok. Good times
![Mike Vanbuskirk avatar](https://avatars.slack-edge.com/2023-06-28/5504120226212_9e82fa588ab015eda5be_72.png)