Skip to content
Snippets Groups Projects
Select Git revision
  • 5098-upgrade-redis-7.x
  • jdrpereira-master-patch-a654
  • jon-ci-rename-and-tidy-up-some-ci-scripts-e5391ed0
  • sh-backport-gitlab-exporter-15.2.0
  • 8-8-stable protected
  • 8-7-stable protected
  • master default protected
  • master-trigger-branch
  • readme-links
  • cf-clarify-primary-secondary-network-requirements
  • 5953-registry-migration-psql-crt
  • 8-9-stable protected
  • sh-document-aks-workload-identity
  • jts/oci-eh
  • fix-dev-com-dependency-on-gitlab-build-images
  • 8-6-stable protected
  • cb-update-prom
  • 487059-cell-configuration
  • ci-use-vcluster-for-qa
  • Alexand-master-patch-063d
  • v8.8.3
  • v8.7.7
  • v8.9.0
  • v8.6.5
  • v8.7.6
  • v8.8.2
  • v8.6.4
  • v8.7.5
  • v8.8.1
  • v8.8.0
  • v8.7.4
  • v8.5.5
  • v8.6.3
  • v8.7.3
  • v8.7.2
  • v8.7.1
  • v8.7.0
  • v8.4.6
  • v8.5.4
  • v8.6.2
40 results

values-gke-minimum.yaml

  • Mitchell Nielsen's avatar
    35090516
    Respect NGINX defaultbackend default (disabled) · 35090516
    Mitchell Nielsen authored and Jason Plum's avatar Jason Plum committed
    Respects that NGINX's defaultbackend component is disabled by default,
    rather than intentionally enabling it.
    
    Further context:
    
    It looks like that component is actually disabled by default upstream.
    In !1690 (merged), there was
    !1690 (52b9e8c0), which explicitly enabled
    defaultbackend because it was inherently enabled prior to that change
    (although I can't find anything yet to confirm that). On that note, the
    defaultbackend image doens't seem to be NGINX-specific based on its path
    in the values file:
    
    ```yaml
    registry: registry.k8s.io
    image: defaultbackend-amd64
    ```
    
    Changelog: changed
    35090516
    History
    Respect NGINX defaultbackend default (disabled)
    Mitchell Nielsen authored and Jason Plum's avatar Jason Plum committed
    Respects that NGINX's defaultbackend component is disabled by default,
    rather than intentionally enabling it.
    
    Further context:
    
    It looks like that component is actually disabled by default upstream.
    In !1690 (merged), there was
    !1690 (52b9e8c0), which explicitly enabled
    defaultbackend because it was inherently enabled prior to that change
    (although I can't find anything yet to confirm that). On that note, the
    defaultbackend image doens't seem to be NGINX-specific based on its path
    in the values file:
    
    ```yaml
    registry: registry.k8s.io
    image: defaultbackend-amd64
    ```
    
    Changelog: changed
Code owners
Assign users and groups as approvers for specific file changes. Learn more.