Content-cache

  • By Canonical IS DevOps
Channel Revision Published Runs on
latest/stable 37 30 Nov 2023
Ubuntu 22.04
latest/edge 44 30 Jan 2024
Ubuntu 22.04
juju deploy content-cache-k8s
Show information

Platform:

Learn about configurations >

  • backend | string

    Required if no ingress-proxy relation is established. The backend to use for site, e.g. "http://mybackend.local:80";.

  • backend_site_name | string

    Backend site name, e.g. mybackend.local. If none given, will work out from the configured 'backend' config above.

  • cache_all | boolean

    By default, we respect upstream cache headers (Cache-Control and Expires). This overrides that and enables caching even if upstream tells us not to. WARNING: It won't cache when Vary: * and Set-Cookies headers are sent in the responses. This option overrides the backend cache time instructions (Expires or max-age) by setting a cache time to 1h (which could be less than the caching instructed by the backend)

  • cache_inactive_time | string

    Default: 10m

    The maximum age/time inactive objects are stored in cache.

  • cache_max_size | string

    Default: 10G

    The size of the Nginx storage cache.

  • cache_use_stale | string

    Default: error timeout updating http_500 http_502 http_503 http_504

    Determines in which cases a stale cached response can be used during communication with the proxied server.

  • cache_valid | string

    Default: 200 1h

    Sets caching time for different response codes.

  • client_max_body_size | string

    Default: 1m

    Override max. request body size (default 1m).

  • site | string

    Required if no ingress-proxy relation is established. The site name, e.g. "mysite.local". If the backend is set and this option is empty then the site will default to the application name.

  • tls_secret_name | string

    The name of the K8s secret to be associated with the ingress resource.