| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| freshen hardcoded IDP addresses | operations/deployment-charts | master | +2 -6 | |
| otelcol: deploy k8sattributes processor | operations/deployment-charts | master | +36 -1 |
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T340551 distributed tracing epic | |||
| Open | None | T321211 distributed tracing v1: tech debt blockers | |||
| Open | None | T365855 Stop hardcoding k8s master (k8s API) endpoint IP addresses |
Event Timeline
Comment Actions
Change #1035756 had a related patch set uploaded (by CDanis; author: CDanis):
[operations/deployment-charts@master] otelcol: deploy k8s attributes processor
Comment Actions
Change #1035756 merged by jenkins-bot:
[operations/deployment-charts@master] otelcol: deploy k8sattributes processor
Comment Actions
Change #1037179 had a related patch set uploaded (by CDanis; author: CDanis):
[operations/deployment-charts@master] freshen hardcoded IDP addresses
Comment Actions
Change #1037179 merged by jenkins-bot:
[operations/deployment-charts@master] freshen hardcoded IDP addresses
Comment Actions
This is basically T287491: Allow to address Kubernetes API servers from NetworkPolicy
IMHO the easiest and less intrusive way to do this with an upstream helm chart is to just add a calico networkpolicy template to the chart (the file could even be prefixed with wmf-) that just creates that one policy. The linked phab task should contain some examples for that.
Comment Actions
I'm triaging this to high as this is the only place where wikikube k8s control-plane IPs are hardcoded and we already forgot about it once. Also it's pretty easy to fix.
Comment Actions
@JMeybohm The best way to fix this is by adding a calico definition to the chart directory in a file whose name starts with wmf-, correct?
Comment Actions
I think so, yes. Something like https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/974158