-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add verify-conformance to apps/ #6357
base: main
Are you sure you want to change the base?
Conversation
2d7f6da
to
0b38794
Compare
kind: Deployment | ||
metadata: | ||
name: verify-conformance-release | ||
namespace: prow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a new dedicated namespace:
k8s.io/infra/gcp/bash/namespaces/ensure-namespaces.sh
Lines 145 to 161 in fa4da59
ALL_APPS=( | |
codesearch | |
elekto | |
gcsweb | |
kettle | |
k8s-io-prod | |
k8s-io-canary | |
k8s-io-packages-prod | |
k8s-io-packages-canary | |
kubernetes-external-secrets | |
perfdash | |
prow | |
publishing-bot | |
slack-infra | |
triageparty-cli | |
triageparty-scalability | |
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ameukam, thank you for taking a look!
As the bot interacts with PRs over at cncf/k8s-conformance, will the secrets be available to be authenticated as prow.k8s.io in a new namespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't currently have a way to authenticate to prow.k8s.io
in the aaa
and we don't have access to the GKE cluster running prow.k8s.io
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ameukam, OK this is good to know.
Would think that coordinating with community github-management to create an OAuth app to then provide the credentials to the bot with is a suitable alternative solution?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The historical approach of this is to request a token for one of the bots managed by github management team. Not sure how they feel about an OAuth app. Feel free to ask them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the historical approach would work just fine, I'll reach out. Thank you!
0b38794
to
01d1e8a
Compare
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
01d1e8a
to
cc40e05
Compare
Renamed app from verify-conformance-release to just verify-conformance, adjusted the deployment too. |
cc40e05
to
ae13e03
Compare
apart of apisnoop donation to sig-architecture
ae13e03
to
e58bfa5
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: BobyMCbobs The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Unsure how to handle the webhook and HMAC side of it. I'm aware of sigs.k8s.io/prow/cmd/hmac but unsure whether it can be used here. |
apart of apisnoop donation to sig-architecture
depends on: kubernetes/test-infra#31804, kubernetes/test-infra#31777
ticket: kubernetes/org#4760 (might need moving to k8s.io?)
TODO
/assign
/hold