Replies: 4 comments
-
talosctl -n NODE get kubeprismstatus -o yaml |
Beta Was this translation helpful? Give feedback.
0 replies
-
Oh - Talos doesn't apply new enabled defaults to existing systems. So if you create a new cluster with Talos 1.6 - it will have KubePrism. But upgrading an older cluster will not enable it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Kubeprism only listens on localhost |
Beta Was this translation helpful? Give feedback.
0 replies
-
Makes sense! Thanks all, ive patched my current config.
…On Fri, Dec 22, 2023, 19:19 Noel Georgi ***@***.***> wrote:
Kubeprism only listens on localhost
—
Reply to this email directly, view it on GitHub
<#8113 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD6RMGXW25EBH6UUH62JATYKZEUTAVCNFSM6AAAAABBAL6DHCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TSMZSGEZDE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a dumb question probably, but here goes. How can i validate if kubeprism is working? I've upgraded from 1.5.5 to 1.6.0, and per https://www.talos.dev/v1.6/kubernetes-guides/configuration/kubeprism/ it says it's enabled by default, but i have nothing in my machineconfigs. I've tried nmaping port 7445 from another host and it says closed, but from the docs it only listens internally. Is there some way to actually verify it's working before i point cilium at it instead of my external HAPROXY Loadbalancer? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions