kubernetes-sigs/apisnoop

Ensure that ghproxy is running and active

Closed this issue · 1 comments

ghproxy was discovered to be not scheduling here
kubernetes-sigs/verify-conformance#47 (comment)
investigate why it isn't scheduling and ensure it's live

closing since verify-conformance will likely run in an existing cluster