Alex
Alex
@andrewdinunzio it seems your issue has 2 proposals in it : 1. Make a separate chart just for cr's which is something that makes sense to me, would you be...
> they would probably be isolated by namespace and within their tenant namespace they would bind a normal namespaced Role to the view ClusterRole just for that namespace. I see...
> I see, so if I understand your point correctly, having an aggregate-to-view/aggregate-to-edit could be a useful addition but you would want it to be disabled by default? Or are...
Meanwhile kps separated the [crds](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack/charts/crds) in the a sub-chart
@pseymournutanix That's a good point and we are aware of it. As we don't actually deploy the cr as part of this chart we should at least update the examples....
I approve. Thanks @jaronoff97
I think this would provide a bridge for existing kps users that otherwise would not care to switch (afaik Prometheus is still used in ~ 99.x% of Kubernetes deployments for...
> I'm not sure how this transitioning chart would work? Should we assume that user installed kube-prometheus-stack and we try to somehow migrate it from that to this chart? We...
@coffeebe4code maybe [this](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/dynatraceexporter) will help?
@puckpuck Thanks for opening this. 1. I think we should disable cert-manager and use self signed cert by default while deploying cert-manager under a feature flag. Would you be willing...