test-infra
test-infra copied to clipboard
kubernetes
migrate `kubeadm` jobs to community cluster
This PR moves the kubeadm jobs to the community owned EKS cluster.
ref: https://github.com/kubernetes/test-infra/issues/29722
/cc @fabriziopandini @neolit123 @SataQiu @pacoxu @RA489
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: neolit123, rjsadow
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~config/jobs/kubernetes/kubeadm/OWNERS~~ [neolit123]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Those jobs were intentionally reverted from EKS because it seems that they are causing node instability issues - https://github.com/kubernetes/k8s.io/issues/5473#issuecomment-1664382707. Please hold this change, we are still investigating.
/hold
We are investigating EKS node instability issue and we have a suspicion that those jobs may cause problem on EKS nodes (https://github.com/kubernetes/k8s.io/issues/5473)
/hold
We are investigating EKS node instability issue and we have a suspicion that those jobs may cause problem on EKS nodes (kubernetes/k8s.io#5473)
those were kubeadm jobs but different ones - periodics. these are presubmits.
but yes, preferably we should not migrate if issues are anticipated!
PR needs rebase.
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.
FTR, the (com. cluster) canaries were just failing on k/kubeadm and we added means to skip them: https://github.com/kubernetes/test-infra/pull/30658 https://github.com/kubernetes/kubeadm/pull/2929
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
@rjsadow: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-test-infra-misc-image-build-test | 07edbfaa395da0242d1a336e69e88537ac0652fe | link | true | /test pull-test-infra-misc-image-build-test |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.