Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BackendConfig.cdn.compressionMode not supported #1908

Closed
mogest opened this issue Jan 21, 2023 · 6 comments
Closed

BackendConfig.cdn.compressionMode not supported #1908

mogest opened this issue Jan 21, 2023 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@mogest
Copy link

mogest commented Jan 21, 2023

Cloud CDN dynamic compression was introduced in October last year, however there is no automatic way yet of enabling it when the backend service is set up by GKE.

It can be manually enabled using

gcloud beta compute backend-services update --global [backend-service-name] --compression-mode=AUTOMATIC

Could this setting be added to BackendConfig?

@cezarygerard
Copy link
Contributor

@spencerhance PTAL

@spencerhance
Copy link
Contributor

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 24, 2023
@spencerhance
Copy link
Contributor

Hi @mogest,

Thanks for your feature request! We would be happy to review a PR for this, however it is unlikely that we will be prioritizing adding this feature in GKE Ingress. However, I would expect to see it in GKE Gateway.

@mogest
Copy link
Author

mogest commented Jan 24, 2023

Thanks @spencerhance. I'll see what I can do with a PR!

@tczekajlo
Copy link

This PR should help with the issue - #2004

@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 20, 2023
@mogest mogest closed this as completed Jul 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants