tailscale: k8s-operator api proxy: remote error: tls: internal error

What is the issue?

Following the process for the kube-proxy functionality here, every step works until kubectl get pods, where the following error output is generated -

E1105 09:55:32.633129   55472 memcache.go:265] couldn't get current server API group list: Get "https://tailscale-operator.XXXX.ts.net/api?timeout=32s": remote error: tls: internal error
E1105 09:55:34.266489   55472 memcache.go:265] couldn't get current server API group list: Get "https://tailscale-operator.XXXX.ts.net/api?timeout=32s": remote error: tls: internal error
E1105 09:55:34.973559   55472 memcache.go:265] couldn't get current server API group list: Get "https://tailscale-operator.XXXX.ts.net/api?timeout=32s": remote error: tls: internal error
E1105 09:55:35.708324   55472 memcache.go:265] couldn't get current server API group list: Get "https://tailscale-operator.XXXX.ts.net/api?timeout=32s": remote error: tls: internal error
E1105 09:55:36.529173   55472 memcache.go:265] couldn't get current server API group list: Get "https://tailscale-operator.XXXX.ts.net/api?timeout=32s": remote error: tls: internal error
Unable to connect to the server: remote error: tls: internal error

Steps to reproduce

Follow steps here, then run any kubectl command, in this example, ‘kubectl get pods’.

Are there any recent changes that introduced the issue?

None.

OS

macOS

OS version

Sonoma 14.1

Tailscale version

1.50.1

Other software

No response

Bug report

BUG-6984ad9c274d166d760a649fec631d5592251cf016784f2db8dac41ab06d616b-20231105150327Z-c70b79c357e70f49

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 26 (13 by maintainers)

Commits related to this issue

Most upvoted comments

Hello, Just wanted to ‘update’ you so to speak, i’ve not forgotten. I just converted my deployment over to a values file and intend to use the helm repo’s directly, instead of a local copy, along with nuking all the config from the test cluster in preparation for testing with the latest version/s.

I’ll try and come back to this properly in the next week or so.