Prerequisites: * kubernetes ingress * your varnish proxy cache * Symfony PHP application 1. Edit your global Kubernetes Ingress Config Map in namespace ingress-nginx named nginx-configuration [https://rancher2.exploit.cz/p/local:p-mt7fw/config-maps/ingress-nginx:nginx-configuration] and add use-forwarded-headers: true 2. In your Varnish proxy in section sub vcl_recvadd if (req.http.
> We recently discovered a bug in the Let's Encrypt certificate authority code, described here: https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591 Unfortunately, this means we need to revoke the certificates that were affected by this bug, which includes one or more of your certificates. To avoid disruption,
You can use quay.io/spaces/kube-httpcache:stable - Github README [https://github.com/mittwald/kube-httpcache/blob/master/README.md] Necessary configuration when RBAC is enabled: * create ServiceAccount: kubectl --kubeconfig kube_config_cluster.yml -n web create serviceaccount varnish-watcher * create ClusterRole + ClusterRoleBinding: kubectl --kubeconfig kube_config_cluster.yml apply -f
I am using RKE cli tool from Rancher for upgrading Kubernetes cluster, but instead of using rancher/nginx-ingress-controller:0.21 I am using kubernetes-ingress-controller/nginx-ingress-controller:0.25.0. In Kubernetes v1.13 kubernetes-ingress-controller/nginx-ingress-controller:0.25.0 works well but stopped after upgrade. You will get this error in ingress
> Poprvé jsem s k8s experimentoval již v roce 2016, tehdy jsem ale nevyřešil neustálé problémy s ETCD. Cluster se vždy do měsíce rozpadl. Když jsem se na přelomu roku 2017/2018 rozhodoval kam dál posunout svoje zkušenosti s Dockerizováním aplikací, Kubernetes (k8s) byla jasná volba. Stál jsem ale před