-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to find documentation for how to migrate prometheus to sds #27996
Comments
God this has been a massive rabbit hole... my next idea was to inject prometheus but effectively disable it as a sidecar
We've modified our injector to support After all that i realised it won't work as prometheus currently lives in Now i'm faced with either manually injecting (complex in our pipeline, we rely in run time injection), or attempting to move prometheus (a nightmare, due to all the things that reference it). |
The above doesn't work, outbound connections fail so it looks like I decided to try
|
|
For anyone coming to this issue; this is how I got this working: https://karlstoney.com/2020/10/15/istio-upgrades-prometheus-sds However the solution in that blog is blocked by this bug: |
Closing this in favour of #28050 |
Bug description
Our (multiple) prometheus servers use the
istio-pilot
created secrets in order to scape istio endpoints. As part of the move toistiod
and subsequentlysds
, those secrets are no longer created.I couldn't find any documentation to help me work out what to do next, until I was pointed at https://istio.io/v1.6/blog/2020/proxy-cert which says to use
.Values.prometheus.provisionPrometheusCert to true
.However
istioctl generate-manifest
on1.6.12
gives you:Error: unknown field "provisionPrometheusCert" in v1alpha1.ExternalComponentSpec:
So I couldn't.
We actually don't use the istio deployment of prometheus anyway, so i was only wanting to inspect the templated output. Instead I started looking at https://github.com/istio/istio/blob/release-1.6/manifests/charts/istio-telemetry/prometheus/templates/deployment.yaml
I can't really decipher what I need to do in order to migrate here.
Have I missed some documentation that clearly explains how people migrate to SDS?
[x] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure
Expected behavior
Clear guidance when making breaking changes.
Steps to reproduce the bug
Version (include the output of
istioctl version --remote
andkubectl version --short
andhelm version
if you used Helm)1.6.12
How was Istio installed?
Helm
Environment where bug was observed (cloud vendor, OS, etc)
The text was updated successfully, but these errors were encountered: