Skip to content

Conversation

Blarc
Copy link
Contributor

@Blarc Blarc commented Jun 11, 2025

If you are not running kube-proxy on a host running the API server, then you must make sure that the system is enabled with the following kube-apiserver flag -https://kubernetes.io/docs/tasks/extend-kubernetes/configure-aggregation-layer/.

Pull Request

What? (description)

Why? (reasoning)

Acceptance

Please use the following checklist:

  • you linked an issue (if applicable)
  • you included tests (if applicable)
  • you ran conformance (make conformance)
  • you formatted your code (make fmt)
  • you linted your code (make lint)
  • you generated documentation (make docs)
  • you ran unit-tests (make unit-tests)

See make help for a description of the available targets.

…deploying without kube-proxy

If you are not running kube-proxy on a host running the API server, then you must make sure that the system is enabled with the following kube-apiserver flag -https://kubernetes.io/docs/tasks/extend-kubernetes/configure-aggregation-layer/.

Signed-off-by: Jakob Maležič <[email protected]>
@github-project-automation github-project-automation bot moved this to To Do in Planning Jun 11, 2025
@talos-bot talos-bot moved this from To Do to In Review in Planning Jun 11, 2025
@smira
Copy link
Member

smira commented Jun 11, 2025

But this is only applicable if you want to use aggregation layer, and most people do not use this I guess?

And those who do want to use it, should be comfortable setting this up correctly?

@smira smira moved this from In Review to On Hold in Planning Jun 11, 2025
@Blarc
Copy link
Contributor Author

Blarc commented Jun 11, 2025

Hey @smira,

I just think it would be maybe wise to mention this somewhere. I needed to add this in order for cert-manager to start working. I'd think a lot of people use cert-manager.

@smira
Copy link
Member

smira commented Jun 12, 2025

I just think it would be maybe wise to mention this somewhere. I needed to add this in order for cert-manager to start working. I'd think a lot of people use cert-manager.

Probably yes, not sure if this is the right place/context, as otherwise we end up rebuilding Cilium/cert-manager docs in Talos

Copy link

This PR is stale because it has been open 45 days with no activity.

@github-actions github-actions bot added the Stale label Jul 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: On Hold

Development

Successfully merging this pull request may close these issues.

2 participants