Karen Almog

I'm running into the same issue. The repo is a public forked repo. The app is installed into the repo. Seeing the following logs in CloudWatch: ``` 2022-08-19 11:53:05.757 DEBUG...

Ok, found the issue - the problem was with the content of `TF_VAR_github_app_key_base64` - I used the wrong value, which explains why logs are complaining about an empty PEM file.

Thank you for this submission! K0s was never tested in IPv6 mode only (only in dual stack mode). We'll have to take a deeper look at how to enable pure...

Can be simply added to the check-basic test

Hey @gakio12 please rebase with the current code updates. Thanks!

After exploring the option for passing in login secrets to the runners (deemed insecure) - we've decided to go the route of automating the creation of ARM runners for every...

https://github.com/k0sproject/k0s-internal/discussions/20

because the upstream PR seem to be stale, I opened https://github.com/etcd-io/etcd/pull/12469

@jekader thank you for this issue. I've added it to our backlog candidates. Additional interesting resources: * https://github.com/carlosedp/riscv-bringup/ * https://carlosedp.medium.com/docker-containers-on-risc-v-architecture-5bc45725624b * https://riscv.org/wp-content/uploads/2019/12/12.10-14.50c-The-RISC-V-Journey-Through-Containers-to-the-Cloud.pdf

I am not convinced that a full listing of all files used by k0s, add meaningful information to the docs. Many of the listed files are auto-generated, and manipulating them...