Marcel Zapf
Marcel Zapf
@tomasodehnal you can also do it via cli. `cloudflared tunnel route dns TUNNELNAME FQDN` and youre done. You can also iterate over the ingress rules via init container to automate...
Just read the log. Your secret is wrong.
I have this same issue. But this works on vsphere so i think its a bug. But there is a workaround to solve this problem: ``` }{% if provision_with_ansible %},...
Same here the vsphere prov deletes the packer vm so i think thats a bug
Hi @chaunceyjiang, of course!! Thank you for you time!! Helm: ``` bgp: enabled: false hubble: enabled: true relay: enabled: true ui: enabled: true ingressController: enabled: true externalIPs: enabled: true k8sServiceHost:...
I test this inside the company and on a rancher and also a vanilla cluster. So this is reproducible.
Thats weird?! Can you also try to delete ingress manifest through argocd?
I have the same problem on kubernetes with prometheus, here I can see extreme cpu usage from the prom-adapter which causes to spike the cpu temps about 30 celsius. 
@bboreham thanks, done. for ref https://github.com/prometheus-community/helm-charts/issues/5747
I would use vault namespaces istead of multiple instances or just more vault sidecars with each configurations for each instance. Or you using the env for configure the avp.