Where to host cs.k8s.io

[ameukam]

https://cs.k8s.io is running on a baremetal server provided by Equinix Metal(ex Packet) under CNCF budget and operated until now by @dims.

The question was asked about whether or not we should host CodeSearch on aaa cluster.

Ref: https://kubernetes.slack.com/archives/CCK68P2Q2/p1615204807111900?thread_ts=1615189697.108500&cid=CCK68P2Q2

Issue open to track the discussions and the consensus about this.

[nikhita]

@dims where is the original source code for cs.k8s.io? 👀

[nikhita]

/wg k8s-infra

[ameukam]

/sig contributor-experience
/priority backlog

/assign @spiffxp
cc @mrbobbytables @alisondy @cblecker @munnerz

[ameukam]

@dims where is the original source code for cs.k8s.io? eyes

@nikhita You can find the config here https://github.com/dims/k8s-code.appspot.com/

[BenTheElder]

What's the argument against hosting it on AAA?

[dims]

@BenTheElder nothing other than someone has to do it :) oh, i don't know how to wire the ingress/dns stuff

i tried a long time ago :) #96

[ameukam]

What's the argument against hosting it on AAA?

I would say lack of artifact destined for aaa (aka no up-to-date container image for hound). We could host the image on k8s-staging-infra-tools.

[nikhita]

@ameukam should this issue be migrated to the k/k8s.io repo?

[ameukam]

@nikhita I'm not sure about the right place of this issue. Just wanted to put this under SIG Contribex TLs and Chairs radar.

[BenTheElder]

it should be under k/k8s.io imho. I think we should host it on AAA fwiw.

[nikhita]

Moving to k8s.io repo. slack discussion - https://kubernetes.slack.com/archives/CCK68P2Q2/p1623300972130500

[spiffxp]

/sig contributor-experience
/wg k8s-infra

[jimdaga]

I took a stab at onboarding codesearch; @spiffxp could I get your input? I want to make sure I didn't miss anything.
I want to stage all the infra, and get it deployed via prow first. Then we can follow up with another PR to cut-over DNS when we are ready.

#2513
kubernetes/test-infra#23201

I could also work on adding the docker build logic after, but I haven't worked in that repo yet so I'll have to do some digging.

cc @dims

[spiffxp]

/priority important-soon
/milestone v1.23

[justaugustus]

What about using https://sourcegraph.com/kubernetes to minimize the maintenance burden here?
This is something I suggested to @dims in the past, but didn't have the bandwidth to do at the time.

[dims]

choices are:

1. leave things where they are
2. move to k8s wg infra
3. redirect to cs.k8s.io to sourcegraph

• i have been taking care of 1 already for a while with minimal downtime, so i am ok with continuing to do so
• if someone wants to do 2, i am happy to work with help, show how things are setup and we can shut down the equinix vm
• i personally don't like option 3, i love the the hound UX, if the consensus is we should go with 3, that is fine with me. I am happy to run a personal instance on a custom domain for myself (community is welcome to use)

if i missed any other options, please feel free to chime in.

[spiffxp]

/unassign

[nikhita]

/remove-lifecycle stale

@jimdaga do you have cycles to address the review on #3679?

[ameukam]

/milestone v.126

[k8s-ci-robot]

@ameukam: The provided milestone is not valid for this repository. Milestones in this repository: [v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

/milestone v.126

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.

[ameukam]

/milestone v1.26

[upodroid]

Can we explore deprecating this in favour of GitHub Code Search?

https://cs.github.com/
https://github.com/features/code-search

[ameukam]

Not really. one issue is that Github CS requires auth to use it while we have anonymous queries using cs.k8s.io (e.g. https://go.k8s.io/owners/dims).

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[BenTheElder]

/lifecycle frozen
closing this is not helpful, unless we've also shut down the existing infra.

[ameukam]

/assign @SohamChakraborty

[k8s-ci-robot]

@ameukam: GitHub didn't allow me to assign the following users: SohamChakraborty.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @SohamChakraborty

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.

[SohamChakraborty]

I think this is now ready for migration from the bare metal server to aaa cluster. I spoke with Arnaud and he will decide on a path for migration.