hosting google/triage-party for sig-release

[ameukam]

SIG-Release is exploring https://github.com/google/triage-party as a triage tool that will help the bug-triage team during release cycles. triage-party is optimized for k8s (or Google Cloud Run) deployments.

What's needed :

• a namespace in aaa cluster and a google group: Add namespace and google for triage party hosting #916
• DNS entries
• TLS certificate
• an Ingress with GCP ip global adress

Persistence need to be discuss but we can start by using local disk.

Ref. kubernetes/sig-release#1073

/assign @spiffxp @thockin @bartsmykla @justaugustus @markyjackson-taulia
/sig release
/area release-eng

[thockin]

No objection - I've been meaning to play with it :)

[ameukam]

triage-party is deployed (see #967) but we're facing an issue with the ingress controller on aaa cluster. Discussion about this on slack : https://kubernetes.slack.com/archives/CCK68P2Q2/p1593722658371200.

[justaugustus]

@ameukam -- triage-party v1.2.0 is out, so we should be able to clear up the health-checking now: https://github.com/google/triage-party/releases/tag/v1.2.0

[ameukam]

@justaugustus 1.2.0 of triage-party is deployed : #1022.

[ameukam]

This is can be closed.
/close

[k8s-ci-robot]

@ameukam: Closing this issue.

In response to this:

This is can be closed.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.