-
Notifications
You must be signed in to change notification settings - Fork 164
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
Feature/prometheus skipper metrics #861
Conversation
| spec: | ||
| containers: | ||
| - name: prometheus | ||
| image: prom/prometheus:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need a compliant image here.
|
@szuecs can we switch one of the dev clusters to this branch and prepare the checks before we start rolling this into dev and further? |
|
@mikkeloscar sure! |
|
volume mount issue: kubernetes/kubernetes#2630 This is a fix for the volume problem |
| emptyDir: {} | ||
| securityContext: | ||
| runAsUser: 65534 | ||
| fsGroup: 65534 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A comment on why this is needed would be good for the future :)
I guess 65534 -> nobody?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I will not change it, because if the nobody user get 42 as uid then this container can not read and write data anymore, because of uid miss match (media has 65534 and uid 42), which should be in theory changed, but better to be sure.
|
Current state is that I found solutions for all metrics we want to provide. |
|
zalando/skipper#569 implemented a soft migration path for enabling users to have both versions of metrics exposed. We can do now the soft migration from codahale to prometheus. |
…nabled in the kubernetes service annotations
feature add migration path from codahal metrics to prometheus
e7d4bb2
to
ec16fdd
Compare
|
👍 |
| @@ -0,0 +1,61 @@ | |||
| apiVersion: apps/v1beta1 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should now be apps/v1 (since v1.9)
| metadata: | ||
| annotations: | ||
| labels: | ||
| application: prometheus |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should have the version label here to be consistent with the other manifests. :)
| template: | ||
| metadata: | ||
| labels: | ||
| application: prometheus |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also version label here :)
|
comments will be fixed in a separate PR |
|
👍 |
This is a breaking change please make sure we only roll this out to dev and not to alpha and beta, before all important zmon checks and alerts have replacements.
This feature enables us to have better aggregated metrics, that are not as complicated as before.
It should also fix the problem of skipper-ingress pod restart will loose all metrics and the aggregation looks awkward.
I am not sure if we should add more prometheus replicas and use a service to make it more resilient to cluster updates, etc.