docs: set apiServer.extraArgs.enable-aggregator-routing

[Blarc]

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.

[smira]

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?

[Blarc]

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]

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