Make new CDN features configurable through the BackendConfig custom resource

[Brradut]

"New" CDN features, like being able to include named cookies or http headers in the cache key, aren't available in the BackendConfig CRD, even though they have been available for more than 2 years through other means.

I considered using other ways of updating the backends (the REST API directly, or wrappers of the API like gcloud, terraform, config-connector, etc.), but the controller removes the extra configuration after it's added.

I'd love it if these features were to be implemented. I wasn't able to find a way to use these features with backends managed by gce-ingress, so any workaround would also be appreciated. 🙏

This can be considered a duplicate of #1766, and #2347 (which have been automatically closed), or a follow-up of #1386. The implementation itself seems like it should be pretty straight-forward.

🫡

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[markmssd]

/remove-lifecycle stale

[TurtleTT]

We urgently need this for our projects!

[NicolasGuary]

Same here, I think it's quite a critical feature that should be addressed. This makes configuring a CDN not viable on my use case.

[codergolem]

We just get blocked from properly using the CDN because configuring the cache-key headers is not possible, this is really urgent.