Page MenuHomePhabricator

Add support to dynamicproxy for kubernetes based web services
Closed, ResolvedPublic


Either via DNS or by writing a simple variant of kube2sky ( that feeds into our proxy system.

Event Timeline

yuvipanda raised the priority of this task from to Needs Triage.
yuvipanda updated the task description. (Show Details)
yuvipanda added subscribers: Aklapper, yuvipanda.
yuvipanda set Security to None.
yuvipanda moved this task from To do to Doing on the Labs-Sprint-115 board.

Change 242448 had a related patch set uploaded (by Yuvipanda):
tools: Add k8s::webproxy to tools::proxy

Change 242448 merged by Yuvipanda:
tools: Add k8s::webproxy to tools::proxy

Change 241908 had a related patch set uploaded (by Giuseppe Lavagetto):
dynamicproxy: add support for kubernetes

Change 241908 merged by Giuseppe Lavagetto:
dynamicproxy: add support for kubernetes is now running on kubernetes!!!! \o/ \o/ \o/ HI5

What do we still need:

  • Download requests with pip3 (needs a pip3 provider or an ugly exec)
  • Provide the kube token via some mechanism like hiera or something.

I'd call only the first as a requirement to consider the ticket resolved.

valhallasw triaged this task as Medium priority.Oct 4 2015, 11:50 AM
valhallasw moved this task from Triage to Backlog on the Toolforge board.
valhallasw added a subscriber: valhallasw.

Do we still need python3-requests that's different? I don't find any actual errors there, but not sure if that's because pip3 already installed requests?

I"m doing the token mechanism now.

Yes, it looks like it's being read from /usr/local (the requests library) so it was definitely imported from pip3...

Let's put in a fixed package in our repos instead....

Ok, so the token authentication is sorted out now \o/

They're also running on a readonly proxy-infrastructure account now!