apps/publishing-bot: automate deployment

[spiffxp]

Followup to #2151

publishing-bot currently won't auto-deploy because it has no deploy.sh, instead it consists solely of a README.md that calls out to: https://github.com/kubernetes/publishing-bot/blob/master/k8s-publishing-bot.md

It would be nice to see if we can get this fully automated. Some suggestions:

• switch from using git-crypt to a secret that is synced in from kubernetes-external-secrets as we're doing for other apps
• make the "hack/fetch-all-latest-and-push.sh kubernetes" step idempotent (if it isn't already) such that it could run each time a deploy happens, vs. needing to run that just when new staging repos are added
• separate out the "build-image push-image" steps to follow the typical cloudbuild-based image building workflow used by other subprojects

/wg k8s-infra
/sig release
/priority important-longterm
/kind cleanup
/area cluster-infra
/area infra/publishing-bot
/milestone v1.23

/assign @nikhita @dims
I'm assigning to you based on membership in k8s-infra-rbac-publishing-bot and being root approvers for kubernetes/publishing-bot

[spiffxp]

FYI @nikhita as of #2829 we're automatically syncing the value of the github token secret from Google Secret Manager, so the publishing-bot repo no longer needs to use git-crypt to store the token.

[ameukam]

/milestone v1.24

[dims]

/assign @justaugustus

[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

[nikhita]

/remove-lifecycle stale

…

On Mon, 2 May 2022 at 02:26, Kubernetes Triage Robot < ***@***.***> wrote: 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 <https://www.kubernetes.dev/docs/guide/issue-triage/> Please send feedback to sig-contributor-experience at kubernetes/community <https://github.com/kubernetes/community>. /lifecycle stale — Reply to this email directly, view it on GitHub <#2430 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD24BUBNDR6OJGVKGHBRO6TVH3VXPANCNFSM5BIWCSTQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ameukam]

/milestone v1.25

[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

[nikhita]

/remove-lifecycle stale

…

On Wed, 10 Aug 2022 at 08:31, Kubernetes Triage Robot < ***@***.***> wrote: 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 <https://www.kubernetes.dev/docs/guide/issue-triage/> Please send feedback to sig-contributor-experience at kubernetes/community <https://github.com/kubernetes/community>. /lifecycle stale — Reply to this email directly, view it on GitHub <#2430 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD24BUBFCG6Q24HSXERPR3LVYMLR5ANCNFSM5BIWCSTQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ameukam]

/milestone clear

[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

[ameukam]

/remove-lifecycle stale
/lifecycle frozen