Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
b
billowy-army-68599
03/18/2020, 4:39 AM@enough-greece-61665 would you mind sharing what your problem and solution was?
e
enough-greece-61665
03/18/2020, 12:46 PMWell, honestly, it's more of a workaround than an actual fix but for now, I disabled all the
ServiceMonitorSo now my call to the chart looks like
const prometheus = new k8s.helm.v2.Chart("po", {
chart: 'prometheus-operator',
repo: 'stable',
version: '8.12.1',
transformations: [removeGrafanaTest, addNamespace(monitoringNamespaceName)],
namespace: monitoringNamespaceName,
values: {
kubeControllerManager: { enabled: false },
kubeEtcd: { enabled: false },
kubeScheduler: { enabled: false },
kubeProxy: {enabled: false},
coreDns: { enabled: false },
prometheusOperator: { createCustomResource: false }
}
}
}and that has at least resulted in things coming up and producing metrics for the entire cluster
ultimately though, we'd like to have those service monitors working...