hh commented 7 months ago

ii maintains everything for APISnoop.cncf.io Ideally this happens within the Kubernetes Community / #sig-k8s-infra

Key Results:

[ ] KR1 - apisnoop website s donated to #sig-k8s-infra
[x] KR2 - the workflow happens completely within the k8s community repositories
[ ] KR3 - APISnoop netlify site moved from CNCF to Kubernetes Community

In order to have community ownership of the apisnoop website

As a #sig-k8s-infra maintainer
I want the apisnoop website to be fully accessible and maintainable by the community

As K8s community member
I want understand how the apisnoop website is deployed and contribute to it

Given a request to change the apisnoop website
When I create a PR to change the logic
Then the workflow happens completely within the k8s community repositories

Steps for this include (all of these can become tickets):

Pare down the APISnoop side to essentials (removing historical org files and experiments)
Ensure all documentation, including scripts, are up to date (or removed) (e.g. steps for setting this up with Kind)
Ensure snoopdb can work with latest version of Postgres/Debian/Python
Fix issue with updating the helm chart upon a new release

hh commented 7 months ago

Let's write up documentation for all the accounts and services required for the apisnoop website

sig-k8s-infra will need a way to provide self-management of those accounts and resources (and how they are deployed and managed)

BobyMCbobs commented 7 months ago

One possible issue during migration that'll need an immediate fix is the use of cncf/apisnoop github user content remote content, see https://github.com/search?q=repo%3Acncf%2Fapisnoop%20raw.githubusercontent.com%2Fcncf%2Fapisnoop&type=code

BobyMCbobs commented 7 months ago

Auto bump the image, so manual updating isn't required https://github.com/kubernetes/test-infra/pull/31749

BobyMCbobs commented 7 months ago

Coordinating with Madhav and might have some changes tomorrow in moving APISnoop into the kubernetes-sigs org

hh commented 7 months ago

Cool beans, where are we coordinating with Madhav (and who are they?) Do we have buy in from #sig-arch yet?

BobyMCbobs commented 7 months ago

Cool beans, where are we coordinating with Madhav (and who are they?)

@hh, see: https://github.com/kubernetes/org/issues/4705#issuecomment-1905549895 I'm unsure why I hadn't linked it in here, although it is on Slack.

He has direct messaged me the instructions. APISnoop must be transferred to the kubernetes-purgatory org, where he will finalise it over to kubernetes-sigs (see: https://github.com/kubernetes/community/blob/fb88d4f2f6b5544c142d9d4eacd349ca89ff477b/sig-contributor-experience/meeting-notes-archive/2022-meeting-notes.md?plain=1#L3039)

Do we have buy in from #sig-arch yet?

We have a +1 from Dims.

hh commented 7 months ago

Interesting! Thanks for the update!

hh commented 2 months ago

We need to migrate the netlify to the Kubernetes owned Netlify account.

ii / cncf-okrs

🟢 :k8s: O3 - community ownership of apisnoop website #6

sig-k8s-infra will need a way to provide self-management of those accounts and resources (and how they are deployed and managed)