Patryk Małek

Just tested [bumping `sigs.k8s.io/controller-tools` to `v0.17.0`](https://github.com/pmalek/crd-ref-docs/commit/5ff434af2b4cbdf77a3cea937ef499cde6346d37) and it seems to do the trick. Any chance we can get https://github.com/elastic/crd-ref-docs/pull/102 merged and then a bump to 0.17.0? @thbkrkr can you help...

> `sigs.k8s.io/controller-tools` has been updated to `v0.17.0` in: > - https://github.com/elastic/crd-ref-docs/pull/122 Thanks! Any chance to release 0.1.1 with these changes?

Related: https://github.com/Kong/go-kong/issues/212

@mflendrich You volunteer yourself to groom this 🪄

Please run `make test.golden.update` to include the change in chart version: https://github.com/Kong/charts/actions/runs/14073289665/job/39429900999?pr=1264

@vitoorgomes Just checking in, do you still want to contribute this change?

Adding the `breaking-change` label and putting into v3 as that would be a breaking change.

No need to extend the telemetry package. It's already capable of sending "fixed payloads", which is done in KIC via: https://github.com/Kong/kubernetes-ingress-controller/blob/513db87cbf94ce66207f74365b502e8cde841357/internal/manager/telemetry/reports.go#L86-L92. It's just a matter of serializing [config](https://github.com/Kong/kubernetes-ingress-controller/blob/96ce87bebd05cb54a1bebc3c6da60129a5bd2298/internal/manager/config.go#L43) or CLI...

Still unimplemented. Patches via kustomize are not always viable (when e.g. the source of truth is in *.go files). To me it looks like it would boil down to extending...

@sbueringer That sounds good 👍 I'm not sure what will be the resulting interface but the approach is sound to me. I can work on that but I won't have...