Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempting to fire up Portainer using Helm chart on Microk8s 1.27 using TLS Cert & key fails #131

Open
RachelAmbler opened this issue Jun 9, 2023 · 0 comments

Comments

@RachelAmbler
Copy link

RachelAmbler commented Jun 9, 2023

I was following the documentation here: https://docs.portainer.io/advanced/ssl.

The secret was created without any errors thus confirming that the public key and private key matched.

microk8s.kubectl create secret tls portainer-tls-secret -n portainer  --cert=/etc/ssl/certs/Bundle.pem  --key=/etc/ssl/private/PrivateKey-Unprotected.pem

secret/portainer-tls-secret created

However Portainer seemed to ignore this when I fired it up until I changed --existingSecret=portainer-tls-secret to tls.existingSecret=portainer-tls-secret.

Now I'm getting :

2023/06/09 11:30PM INF main.go:568 > encryption key file not present | filename=portainer
2023/06/09 11:30PM INF main.go:602 > proceeding without encryption key |

in the Pod's logs.

My understanding from this is that go only allows one to pass an unencrypted private key. So it would seem that I'm doing the correct thing, but Portainer's not a happy bunny about it.

Any idea what I'm doing wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant