Github Token for publishing bot to interact with GH repos

[sayanchowdhury]

Organization or Repo

https://github.com/kubernetes/publishing-bot/

User affected

No response

Describe the issue

We are working on running publishing-bot as a periodic job on the test-infra [1]. The publishing-bot would be interacting with the Github repositories through a Github token. The idea is to create a secret with the token and deploy it in the k8s-infra-prow-build-trusted cluster.

The publishing bot is currently running in a cluster named aaa and this cluster already contains a secret publishing-bot-github-token which is a github token that has write access to the staging repositories.

We would like to know if the same token can be reused in the k8s-infra-prow-build-trusted cluster for running the publishing bot or should we file a request for a new token?

[1] kubernetes/publishing-bot#353

/cc @akhilerm

[ameukam]

I don't see any issue on reusing the token in the aaa cluster. Let's get input from the Github admins.

cc @MadhavJivrajani @palnabarun @Priyankasaggu11929

[nikhita]

I'm good with this. Let's wait until EOD for any blocking comments.

If there are none, please go ahead with this.

[Priyankasaggu11929]

I don't see any issue on reusing the token in the aaa cluster.

+1.

Just confirming, is this the only spot we're using the existing publishing-bot-github-token right now?

[MadhavJivrajani]

+1 on reusing the token from the aaa cluster.

[mrbobbytables]

+1 on reusing as well

[sayanchowdhury]

@Priyankasaggu11929 Yes, this is only place the where the token is being used. @akhilerm Could you confirm this info once?

[ameukam]

Token is available on the build cluster: kubernetes/k8s.io#5950

[sayanchowdhury]

Thanks @ameukam. I go ahead and close this issue.

/close

[k8s-ci-robot]

@sayanchowdhury: Closing this issue.

In response to this:

Thanks @ameukam. I go ahead and close this issue.

/close

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.