registry.k8s.io autodeploy

[BobyMCbobs]

registry.k8s.io (currently at https://github.com/kubernetes-sigs/oci-proxy) production and staging should both be managed in a GitOps way.

Related: #4119

[hh]

Existing prow jobs:

• https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes/sig-k8s-infra/oci-proxy
• https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/k8s-staging-infra-tools.yaml#L2

[ameukam]

/sig k8s-infra
/milestone v1.26
/area infra
/priority important-soon

[BobyMCbobs]

This must wait until there's the kubernetes/registry.k8s.io repo, for not repeating migration.

[BenTheElder]

I guess kubernetes/registry.k8s.io#76 is a dupe.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[riaankleinhans]

I guess kubernetes/registry.k8s.io#76 is a dupe.

/remove-lifecycle stale

@BobyMCbobs should we keep this open or can it be closed in favour of #76 ?

[ameukam]

/close

As duplicate of kubernetes/registry.k8s.io#76.

[k8s-ci-robot]

@ameukam: Closing this issue.

In response to this:

/close

As duplicate of kubernetes/registry.k8s.io#76.

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.