davidmirror-ops / flyte-the-hard-way

Prepare requirements and deploy Flyte using Helm
Creative Commons Zero v1.0 Universal
57 stars 15 forks source link

Issue setting up local kubernetes cluster #2

Closed cuevasclemente closed 9 months ago

cuevasclemente commented 9 months ago

Hi,

I'm using MacOS 14.0, and I'm using an Ubuntu 22.04 LTS image:

> sw_vers
ProductName:            macOS
ProductVersion:         14.0
BuildVersion:           23A344

> multipass list
Name                    State             IPv4             Image
k3s-master              Running           192.168.64.3     Ubuntu 22.04 LTS
                                          10.42.0.0
                                          10.42.0.1

I'm trying to follow the on-premises deployment guide to do a local test of a Flyte RawContainer task. I'm having trouble following along with docs/on-premises/001-configure-local-k8s.md. I've gotten up to step 6 without incident.

After setting up my local $HOME/.kube/config, I get two classes of error. When I just run kubectl get pods I get:

E0105 18:09:12.922633   34737 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0105 18:09:12.924260   34737 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0105 18:09:12.925656   34737 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0105 18:09:12.926870   34737 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0105 18:09:12.928057   34737 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
Unable to connect to the server: tls: failed to verify certificate: x509: certificate signed by unknown authority

I read online that there is a way to avoid some issues around tls certificates so I also tried:

kubectl get pods --insecure-skip-tls-verify
E0105 18:06:12.423605   34435 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0105 18:06:12.425427   34435 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0105 18:06:12.427155   34435 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0105 18:06:12.428775   34435 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0105 18:06:12.430551   34435 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
error: You must be logged in to the server (the server has asked for the client to provide credentials)

Any help would be appreciated! Thanks.

cuevasclemente commented 9 months ago

I was able to resolve this and made a PR to fix the bit of the documentation that might have helped me avoid this error.