-
Notifications
You must be signed in to change notification settings - Fork 813
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
hook up build clusters to prow staging instance #1475
Comments
I would hold off on this until you've documented more of a transition plan. To date, I'm not sure we have successfully had two prow service clusters pointed at the same build cluster. There are a number of potentially-dueling prow components to consider. @chaodaiG was looking into this recently for a different prow/build-cluster for a different project (ref: kubernetes/test-infra#14343) The issue I am aware of off the top of my head is that |
As discussed during SIG testing meeting on 02/23/2021, we can deploy the staging again |
Add namespaces to prow build clusters that will be used by the prow staging instance. We are experimenting with the possibility that more than one prow instance can run against the same build cluster. Ref: kubernetes#1475 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
/milestone v1.22 |
Ref: kubernetes#1475 Umbrella issue: kubernetes#1394 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
/milestone v1.23 |
Ref: kubernetes#2559 Part of kubernetes#1475 It's possible the kubeconfig is incorrectly parsed. Testing this theory. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
This was blocked by #2559. /close |
@ameukam: Closing this issue. In response to this:
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. |
Part of #1394
aaa
cluster has network access tok8s-infra-prow-build
andk8s-infra-prow-build-trusted
build clustersk8s-infra-prow-build
andk8s-infra-prow-build-trusted
and them as secrets in namespaceprow
(inaaa
cluster). see prow doc/area prow
/sig testing
/wg k8s-infra
The text was updated successfully, but these errors were encountered: