k8s.io
k8s.io copied to clipboard
cs.k8s.io is 502
Just noticed that cs.k8s.io is returning Bad Gateway. Not sure what's wrong there, filing an issue so that we look into it after Kubecon.
We had an issue with the instance hosting it. I think everything is back to normal:
curl -I https://cs.k8s.io/
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 25 Oct 2022 11:54:05 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
when you see this, you can use cs-canary.k8s.io
This is just me being curious, is codesearch availability a priority or something worth having a backlog issue for?
It's a priority for GitHub Admin Team since they have search snippets based on cs.k8s.io
. e.g. go.k8s.io/owners/dims
https://cs.k8s.io/?q=foo&i=nope&files=&excludeFiles=&repos= seems to be working
No issue until now. I'm gonna close this.
/close
@ameukam: Closing this issue.
In response to this:
No issue until now. I'm gonna close this.
/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.