Michel Loiseleur

Unless I'm missing something, It looks like a crd registry. @hjoshi123 Wdyt about #4598 approach ?

See https://github.com/kubernetes-sigs/external-dns/issues/4575#issuecomment-2198049172

In other well known software, the pattern I see is more to have separation of concerns: 1. In _cert-manager_, there are multiple CRDs, one for `Certificate`, one for `CertificateRequest`, etc....

You're right, for simplicity, the template is using only 1 route. If we change this, it would be breaking for everyone. We’re unsure about the use case and the traction...

Fixed with #4904 /close

/remove-lifecycle stale

/remove-lifecycle stale

BTW, there is already an e2e test using it: https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/main/test/e2e/data/ccm/gce-cloud-controller-manager.yaml

Default kubernetes install with [chart](https://github.com/traefik/traefik-helm-chart) is already non-root and secured on pod level with ```yaml securityContext: allowPrivilegeEscalation: false capabilities: drop: - ALL readOnlyRootFilesystem: true ``` and on deployment level with:...

> Yes, and when running it and trying to bind to a service port (