Add pull-kops-aws-distro-al2023-canary for testing CI changes
Follow up on https://github.com/kubernetes/kops/pull/17520 based on discussion with @ameukam
This job should run in the kops-ci account as it doesn't have the AWS present. We can't test https://github.com/kubernetes/kops/pull/17520 with the current account which is in the CNCF org because there's an org level policy forbidding creating public access buckets in the org.
/assign @ameukam @hakman @rifelpet
/hold for @ameukam to take a look
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hakman, xmudrii
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~config/jobs/kubernetes/kops/OWNERS~~ [hakman]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Youll probably need to add this job to a new file that doesn't get overwritten by build_jobs.py. Perhaps a kops-presubmits-misc.yaml
New changes are detected. LGTM label has been removed.
@ameukam @rifelpet Comments addressed, PTAL
@xmudrii: The following tests 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-unit-test | 004657b440716359326eff2721679454dce3697d | link | true | /test pull-test-infra-unit-test |
| pull-test-infra-unit-test-race-detector-nonblocking | 004657b440716359326eff2721679454dce3697d | link | false | /test pull-test-infra-unit-test-race-detector-nonblocking |
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-sigs/prow repository. I understand the commands that are listed here.
I think there are still some minor issues to pass the tests.
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