This message was deleted.

Hi @David Kortleven, welcome 🙂 Can you share the error you’re getting ? Just to be sure, when you sealed the SSH key as a secret , did you make sure to encode it as instructed in the docs (replace new-line with underscore)?

Thanks for the quicky reply! The error I'm getting is this one:

failed exit status 1: Error: template: opal/templates/secret-envsecrets.yaml:8:78: executing "opal/templates/secret-envsecrets.yaml" at <"_">: wrong type for value; expected string; got map[string]interface {} Use --debug flag to render out invalid YAML

Also, I did not replace the newline with underscore, so that would probably be the next error I will encounter 😅

I’m not a k8s / helm expert (@Raz Co would probably be able to help more when he’s back online) But this seems to be a common trouble with sealed-secrets: https://github.com/bitnami-labs/sealed-secrets/issues/650 And we can either change the helm chart (you can start with a fork), or use a post-render with kustomize

Ah that helps a lot, we will look into it!

I’ll take a look at this shortly, let me know if what Or sent you helps :)

Thanks, I think the answer of Or will get us a long way. I'm out of office next week, so after that I'll try to do one of the suggested options in a fork of the helm chart.

So first, we are planning to add support with custom secrets inside the helm chart so it’ll be easier to maintain secrets in the near future. Second, we’re about to release a major OPAL version in the next few months and we are planning to put much more effort in the deployment types and support more tools, so Kustomize can be a good option to start with ! Moreover, OPAL is an open source project, so any contribution of your team, in any kind, will be very appreciated 🙂