Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support KubePrism endpoint on Talos #3470

Open
Pythoner6 opened this issue Aug 20, 2024 · 1 comment
Open

Support KubePrism endpoint on Talos #3470

Pythoner6 opened this issue Aug 20, 2024 · 1 comment

Comments

@Pythoner6
Copy link

On Talos, it is recommended to pass the KubePrism endpoint to CNI components etc. https://www.talos.dev/v1.7/kubernetes-guides/configuration/kubeprism/

Expected Behavior

Setting the kubernetesServiceEndpoint to the KubePrism endpoint (localhost:7445) should work

Current Behavior

Because some components like the kube controllers do not run in host network mode, these containers fail when trying to access that endpoint. There does not appear to be any way to separate out using different endpoints for the host network vs non-host network cases as is.

Possible Solution

Add a new Talos Provider which can handle the case of using the KubePrism endpoint on Talos, similar to how the Docker EE provider handles using proxy.local here https://github.com/tigera/operator/blob/master/pkg/controller/k8sapi/k8s-endpoint.go#L54.

Another possible solution would be to allow configuring a host mode endpoint and a non-host mode endpoint which might be a bit more generic and wouldn't require special casing for Talos.

Context

Your Environment

  • Operating System and version: Talos 1.7.6
  • Link to your project (optional):
@Pythoner6
Copy link
Author

I went ahead and played around with the adding a talos provider route here Pythoner6@9ea4bf3 - if that looks like the right direction I'm happy to create a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant