Mathieu Massé comments

Results 26 comments of


                                            Mathieu Massé

[kube-prometheus-stack] Unable to get Grafana alerts working

Keeping this open until I can test it with the latest chart version

[kube-prometheus-stack] Unable to get Grafana alerts working

Can this be reopened I can't do it myself

[kube-prometheus-stack] Unable to get Grafana alerts working

Bump

[kube-prometheus-stack] CRDs are not being installed by chart

True about helm can only install CRDs but why not create a kubernetes job to update/install the CRDs, other charts do that with the help of: ```yml annotations: "helm.sh/hook": post-install,post-upgrade,post-rollback...

[kube-prometheus-stack] CRDs are not being installed by chart

The place where I got this from does make use of a flag to enable CRD upgrade so yeah should be something that is configurable.

[kube-prometheus-stack] CRDs are not being installed by chart

Bump

Updating an `azurerm_automation_runbook` causes subsequent `terraform apply` to want to recreate the associated `azurerm_automation_job_schedule`

Hi @mybayern1974, it is the same issue has #7130 but it seems it came back in 2.24.0. After every runbook updates the linked schedule still needs to be recreated. Can...

Updating an `azurerm_automation_runbook` causes subsequent `terraform apply` to want to recreate the associated `azurerm_automation_job_schedule`

@mybayern1974 Can you reopen the ticket I don't have the option to.

Updating an `azurerm_automation_runbook` causes subsequent `terraform apply` to want to recreate the associated `azurerm_automation_job_schedule`

Still a problem with 2.49.0, is this going to be looked into?

All resource including output resources are now checked

Any idea when this will be looked at, this is causing a lot of unnecessary log entries and calls to vault for fetching local variables which always return no result.