Abu Belal

Go to definition for class and class methods do not work on ps core

Agreed, it would be much better to provide both versions. Right now we're managing with some difficult with relatively small code base, but can't imagine how complex it will be...

for anyone else that comes across this I ended up with values.yaml ``` controller: service: annotations: service.beta.kubernetes.io/azure-dns-label-name: "" ``` main.tf ``` set_string { name = "controller.service.annotations.service\\.beta\\.kubernetes\\.io/azure-dns-label-name" value = "${var.domain_name_label}" }...

This is a huge problem when a subscription contains hundreds of resources. There's not much we can do as the call to Azure is handled by `Export-AzRuleData`.

I've got it working with slightly less verbs (code below is terraform) ```hcl rule { api_groups [""] resources = ["services/proxy"] resource_names = ["prometheus-operated:9090"] verbs = ["get", "list", "watch", "create"] }...

That would be difficult as the exporter is generic, it get's metrics for anything in Azure that's made available for API therefore you'd need a dashboard here for all resource...

> https://github.com/juicedata/juicefs juicefs is similar to objectivefs > > > > **update:** > > I tested juicefs for poor random read performance and it should not work as a storage...

How would one specify to the operate to use an additional alertmanager via DNS? for example, by default the operator creates this ``` spec: containers: - args: - --cluster.peer=alertmanager-prometheus-operator-stg-alertmanager-0.alertmanager-operated.monitoring.svc:6783 ```...

@wdarko1 is there any timelines when we can expect this in GA?