Closed Bug 1600670 Opened 5 years ago Closed 4 years ago

Find a way to upstream our ingress config

Categories

(Cloud Services :: Operations: Taskcluster, task)

Product:
Cloud Services
Component:
Operations: Taskcluster
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: brian, Assigned: oremj)

Details

We replace https://github.com/taskcluster/taskcluster/blob/master/infrastructure/k8s/templates/ingress.yaml with https://github.com/mozilla-services/cloudops-infra/blob/master/projects/taskcluster/k8s/chart_overrides/taskcluster/ingress.yaml at deploy time in order to send traffic through iprepd-nginx instead of directly from the GCLB to taskcluster.

Doing it this way is hacky. We should find a way to get the ingress config we actually us in the upstream taskcluster repo. I don't think we can just replace what is there, since then it would not work for anyone else (sinc ehtey won't be using iprepd-nginx).

Summary: Find a way to our ingress config → Find a way to upstream our ingress config
Assignee: nobody → bpitts
Assignee: bpitts → oremj
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.