@markmcgookin Interesting stuff - what are you going to do with your cluster now?

Also - this may not help your particular situation but specifying `--write-kubeconfig-mode` can specify file permissions on the .kube/config file. Might save you a step. Something like:

curl -sfL get.k3s.io | sh -s - --write-kubeconfig-mode 644

@OpinionatedGeek yeah I always forget I can do that and have to do it this way. This cluster has been gathering dust for a while so reimaged the machines. I have a linode cluster running an api a website and a database but I barely use it and it costs about £60 a month. So going to see if I can use ngrok to expose this cluster safely and just fire a cname to the domain via DNS… if it works I can kill my expensive linode cluster.

@markmcgookin Sounds like an excellent money-saving plan - good luck!

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.