Dan Constantinescu

> Thanks for opening this issue. I just wanted to note that if you have ACLs enabled then verify_incoming isn't strictly required for security since an ACL token is required...

> With the upcoming Consul 1.9 release, we are adding the ability to view prometheus metrics in the Consul UI so we will be looking at deeper prometheus support in...

Starting having this issue again with helm Version:"v3.7.2". In previous versions I used to carry a null configuration key as such. ``` livenessProbe: httpGet: exec: command: - /bin/bash - -exc...

The bigger issue here is making sure the pods end-up in the zone they are configured for and fortunately the chart supports a nodeSeletor label. Following on the example above,...

> When you use a different helm release name the name also changes also with Kubernetes namespaces I don't see any Issue You'd want a single helm deployment release, otherwise...

Yeah, memberlist is another one, I use etcd so I don't have that problem. The idea is to create a dynamic config file in Cortex and add the zone awareness...

> Do you wanna give that a go I'm looking into it. Do you want the webhook config/deployment added to the chart with a zone_aware_enabled flag around it ? >...

> I mean we could do our part here and maybe have a guide that references the controller that you would have to setup yourself That'd be the cleanest approach,...

@kd7lxl - there is one fundamental issue with the idea of using an admission controller: at the time the API request makes it through the controller, there is no decision...

I'm not sure the API service would run the resource admission twice through the admission controller between steps 3 and 4 like you've described. In fact what I see happening...