Jayapriya Pai

Results 241 comments of Jayapriya Pai

/unassign since I didnt get enough time to work on this

Updating the secret is needed when changes are made to ServiceMonitors/PodMonitors/Probe or the Prometheus resource itself. More details in https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/design.md#prometheus

There is already discussion around `hostNetwork` support in https://github.com/prometheus-operator/prometheus-operator/issues/2630 and I see that is added in agenda for next [office hours meeting](https://github.com/prometheus-operator/prometheus-operator/blob/main/CONTRIBUTING.md#office-hours-meetings)

I was trying with ```go //+kubebuilder:validation:Pattern:="(.*)" //+kubebuilder:default=; Separator string `json:"separator,omitempty"` ``` But since string default is empty string, it will break the configs which doesn't specify value for separator since...

Currently scaling down [shards](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/shards-and-replicas.md) will not reshard data onto remaining instances. It must be manually moved. I think we need to figure out the best approach if we need to...

The operator version used is a bit old. There may be issues fixed in newer versions. Can you try to use any of the latest version of operator?

I haven't worked much with helm charts. But If you are using [Prometheus community helm chart](https://github.com/prometheus-community/helm-charts/tree/main/charts%2Fkube-prometheus-stack) latest version of chart would be deploying latest version of Prometheus operator ie `0.58.0`...

@gmendesnip Could you please let us know what version of prometheus-operator version you are using? Telegram support was added in `0.57` only

From issue description I see `Image: docker.io/bitnami/prometheus-operator:0.56.2-debian-10-r0` that looks to be different Could you please check version is right from prometheus-operator deployment?