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

traefik-config.yaml cannot be used with k3s local-path? #48

Closed
shrinedogg opened this issue Apr 19, 2021 · 0 comments
Closed

traefik-config.yaml cannot be used with k3s local-path? #48

shrinedogg opened this issue Apr 19, 2021 · 0 comments
Labels
question Further information is requested

Comments

@shrinedogg
Copy link

shrinedogg commented Apr 19, 2021

Seems I'm affected by the error mentioned in your comments: level=error msg="The ACME resolver \"cloudflare\" is skipped from the resolvers list because: unable to get ACME account: open /certs/acme.json: permission denied" when not using the init-container.

Problem is, when using the init-container I face other errors that prevent a successful deployment that I'm struggling to sort out.

When using your manifests verbatim, my traefik pod cannot mount the PVC as k3s local-path and Mayastor NVMF (the two storageclasses available to my cluster) do not support the ReadWriteMany access mode as listed in your traefik-config....

  accessModes:
  - ReadWriteMany
  - ReadWriteOnce

If I comment out the init-container, everything comes up but then I get the error at the top about permissions denied.

Some things I've tried...

  1. Limiting the configfile to either RWM or RWO access modes only
  2. Changing the command in the busybox init-container from chmod -Rv 600 /certs/* to chmod -Rv 600 certs
  3. Update busybox container to 1.32.0
  4. Add storageclass to the PVC to use either local-path or nvmf (mayastor)
  5. Officially complain on github ;)

Thanks for any assistance/ideas you can provide!

@timothystewart6 timothystewart6 added the question Further information is requested label May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants