🌱 Add .prow.yaml, migrate to kcp-prow

[embik]

Summary

This PR moves this repository to the new kcp-prow (also see kcp-dev/infra#25). It uses ghcr.io/kcp-dev/infra/build:1.19.9-1, a base image we are building from https://github.com/kcp-dev/infra/tree/main/images/build.

Also see openshift/release#39766 for removing this repository from openshift-ci.

Related issue(s)

Fixes kcp-dev/infra#29

[openshift-ci]

Hi @embik. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[kcp-ci-bot]

Hi @embik. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[embik]

/cc @xrstf

[nikhita]

We can also remove the github actions workflows in this PR, right?

[embik]

We can also remove the github actions workflows in this PR, right?

Good question, but I would assume we want to keep validation for e.g. the PR type, so do we want to convert that logic into a prow job?

[nikhita]

Good question, but I would assume we want to keep validation for e.g. the PR type, so do we want to convert that logic into a prow job?

I think we can keep it as-is. It uses the one from Kubernetes - https://github.com/kubernetes-sigs/kubebuilder-release-tools/blob/master/.github/actions/verifier/action.yml.

Keeping it as-is would make us consistent with upstream 👍

[xrstf]

/ok-to-test

[sttts]

/lgtm
/approve

[kcp-ci-bot]

LGTM label has been added.

Git tree hash: da031a2d66296019f0c020cece06e0d9dc8d5bb5

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sttts]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sttts]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[xrstf]

/override ci/prow/boilerplate

[kcp-ci-bot]

@xrstf: Overrode contexts on behalf of xrstf: ci/prow/boilerplate

In response to this:

/override ci/prow/boilerplate

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.

[openshift-ci]

@xrstf: Overrode contexts on behalf of xrstf: ci/prow/boilerplate

In response to this:

/override ci/prow/boilerplate

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.

[xrstf]

/override ci/prow/codegen
/override ci/prow/lint
/override ci/prow/unit

All overridden jobs are part of the new Prow jobs already and since the ci-operator.yaml was removed, there is no chance of these tests succeeding.

[kcp-ci-bot]

@xrstf: Overrode contexts on behalf of xrstf: ci/prow/codegen, ci/prow/lint, ci/prow/unit

In response to this:

/override ci/prow/codegen
/override ci/prow/lint
/override ci/prow/unit

All overridden jobs are part of the new Prow jobs already and since the ci-operator.yaml was removed, there is no chance of these tests succeeding.

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.

[openshift-ci]

@xrstf: Overrode contexts on behalf of xrstf: ci/prow/codegen, ci/prow/lint, ci/prow/unit

In response to this:

/override ci/prow/codegen
/override ci/prow/lint
/override ci/prow/unit

All overridden jobs are part of the new Prow jobs already and since the ci-operator.yaml was removed, there is no chance of these tests succeeding.

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.