Take ownership of the Helm repo on Artifact Hub

[stevehipwell]

Is your feature request related to a problem?/Why is this needed
The Helm repo wasn't discoverable on Artifact Hub so I've added the repository, but it now needs it's ownership to be taken over by the Kubernetes Artifact Hub organisation. The repo needs to be verified and the software to be flagged as official.

Describe the solution you'd like in detail

Describe alternatives you've considered

Additional context

[mauriciopoppe]

I'm not familiar with artifact release ownership, I searched in slack and it looks like it's part of sig-release but it looks like there's no process in place for this in k8s yet from https://app.slack.com/client/T09NY5SBT/C2C40FMNF/thread/C2C40FMNF-1688491733.623769

[stevehipwell]

@mauriciopoppe there is a process; see artifacthub/hub#1684.

[stevehipwell]

@mauriciopoppe the Slack thread is about publishing the Helm charts as OCI artifacts which would be new code. I'm referring to getting the existing publishing method to show up correctly in Artifact Hub. One of the steering committee should be able to take ownership of the repository for the Kubernetes Artifact Hub org. Then (or before for that matter) we need to add a artifacthub-repo.yml to the root of the gh-pages` branch as documented in the verify link above. Finally a maintainer should be able to apply for official status.

[mauriciopoppe]

I reached out through email to the steering committee to check about the ownership, hopefully they can help take ownership of the repo

[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

[stevehipwell]

/remove-lifecycle stale

[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

[stevehipwell]

/remove-lifecycle stale

[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