Closed Bug 1562915 Opened 6 years ago Closed 6 years ago

Setup iprepd-nginx for taskcluster

Categories

(Cloud Services :: Operations: Taskcluster, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: brian, Assigned: brian)

References

Details

Currently we have the GCLB routing directly to taskcluster services. We need to add iprepd-nginx in the middle.

We need to make this optional, since not all taskcluster deployments will use iprepd. I suppose this means two ingress configs, one for GCLB->service and one for GCLB->nginx->service. Then we could add an option to helmit to choose which ingress to use.

The iprepd-nginx config will live in the cloudops-infra repo. We'll have to modify our existing helm library to support passing in a custom configmap, since as weitten now it can only proxy to one service but taskcluster has many.

Component: Services → Operations: Taskcluster
Product: Taskcluster → Cloud Services
Version: unspecified → other

I'll add this to community after sorting out some comments from the review.

This is now in place for both running deployment and merged.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.