Skip to content
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

Migrate to Community CI By August 1st #920

Closed
BenTheElder opened this issue Jun 21, 2024 · 12 comments
Closed

Migrate to Community CI By August 1st #920

BenTheElder opened this issue Jun 21, 2024 · 12 comments
Assignees

Comments

@BenTheElder
Copy link
Member

BenTheElder commented Jun 21, 2024

Node problem detector CI still needs migrating, per https://groups.google.com/a/kubernetes.io/g/dev/c/p6PAML90ZOU

You can find node problem detector jobs listed in:

https://github.com/kubernetes/test-infra/blob/master/docs/job-migration-todo.md

(see e.g. jobs with name containing "npd")

@wangzhen127
Copy link
Member

/cc @wangzhen127

@wangzhen127
Copy link
Member

wangzhen127 commented Jul 1, 2024

The following tests still need migration:

  • CI:
    • ci-npd-build
  • presubmit:
    • pull-npd-e2e-node
    • pull-npd-e2e-kubernetes-gce-gci
    • pull-npd-e2e-kubernetes-gce-gci-custom-flags
    • pull-npd-e2e-kubernetes-gce-ubuntu
    • pull-npd-e2e-kubernetes-gce-ubuntu-custom-flags

kubernetes/kubernetes#119211 tracked the issues we encountered previously.

@wangzhen127
Copy link
Member

/cc @DigitalVeer, @AnishShah, @cwangVT

@wangzhen127
Copy link
Member

/assign @DigitalVeer

@k8s-ci-robot
Copy link
Contributor

@wangzhen127: GitHub didn't allow me to assign the following users: digitalveer.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @DigitalVeer

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-sigs/prow repository.

@wangzhen127 wangzhen127 self-assigned this Jul 1, 2024
@wangzhen127
Copy link
Member

I will work with @DigitalVeer to look into this.

@wangzhen127
Copy link
Member

There is also similar work tracked in kubernetes/test-infra#31794

@BenTheElder
Copy link
Member Author

Yeah, kubernetes/test-infra#31794 was tracking the community migrating it, raised here for visibility that the deadline is approaching.

I spoke with @wangzhen127 and another colleague about this, we'll get this pushing to a community bucket and migrate over.

/assign

#925 will make the problem a bit simpler.

@BenTheElder
Copy link
Member Author

OK so after #925, I spoke to my fellow SIG K8s Infra TLs.

There is a gs://k8s-staging-npd already created for NPD in k8s infra, since we're not using it for publishing binaries (thank you!) we can add IAM permission to prow to upload there from the community cluster and switch the scripts over.

That, plus no longer pushing to GCR from CI, should fix everything.

The IAM is managed in https://github.com/kubernetes/k8s.io, can take a look at this later and then we can see about switching buckets.

@BenTheElder
Copy link
Member Author

Filed kubernetes/k8s.io#7007 to allow k8s-infra-prow-build jobs to push to k8s-staging-npd

@BenTheElder
Copy link
Member Author

@wangzhen127
Copy link
Member

Thanks a lot for the work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants