rke2-charts/packages/rke2-ingress-nginx/generated-changes/patch/values.yaml.patch

59 lines
2.0 KiB
Diff

--- charts-original/values.yaml
+++ charts/values.yaml
@@ -3,8 +3,8 @@
##
controller:
image:
- repository: k8s.gcr.io/ingress-nginx/controller
- tag: "v0.35.0"
+ repository: rancher/nginx-ingress-controller
+ tag: "nginx-0.35.0-rancher2"
digest: sha256:fc4979d8b8443a831c9789b5155cded454cb7de737a8b727bc2ba0106d2eae8b
pullPolicy: IfNotPresent
# www-data -> uid 101
@@ -35,7 +35,7 @@
# Optionally change this to ClusterFirstWithHostNet in case you have 'hostNetwork: true'.
# By default, while using host network, name resolution uses the host's DNS. If you wish nginx-controller
# to keep resolving names inside the k8s network, use ClusterFirstWithHostNet.
- dnsPolicy: ClusterFirst
+ dnsPolicy: ClusterFirstWithHostNet
# Bare-metal considerations via the host network https://kubernetes.github.io/ingress-nginx/deploy/baremetal/#via-the-host-network
# Ingress status was blank because there is no Service exposing the NGINX Ingress controller in a configuration using the host network, the default --publish-service flag used in standard cloud setups does not apply
@@ -44,7 +44,7 @@
# Required for use with CNI based kubernetes installations (such as ones set up by kubeadm),
# since CNI and hostport don't mix yet. Can be deprecated once https://github.com/kubernetes/kubernetes/issues/23920
# is merged
- hostNetwork: false
+ hostNetwork: true
## Use host ports 80 and 443
## Disabled by default
@@ -301,7 +301,7 @@
configMapKey: ""
service:
- enabled: true
+ enabled: false
annotations: {}
labels: {}
@@ -540,8 +540,8 @@
enabled: false
image:
- repository: k8s.gcr.io/defaultbackend-amd64
- tag: "1.5"
+ repository: rancher/nginx-ingress-controller-defaultbackend
+ tag: "1.5-rancher1"
pullPolicy: IfNotPresent
# nobody user -> uid 65534
runAsUser: 65534
@@ -661,3 +661,6 @@
##
udp: {}
# 53: "kube-system/kube-dns:53"
+
+global:
+ systemDefaultRegistry: ""