capo: add e2e full test

[lentzi90]

This adds a job for "e2e full" (similar to what CAPI has) and makes the default e2e focus on PR-Blocking tests (again similar to CAPI).

The point it not to change the behavior of current tests, but to allow adding more tests that doesn't need to run all the time.

x-ref:

• Tag current tests as PR-Blocking: 🌱 Tag current e2e tests as PR-Blocking kubernetes-sigs/cluster-api-provider-openstack#1390
• Add more e2e tests that would be part of the e2e full: 🌱 Add e2e clusterctl upgrade tests kubernetes-sigs/cluster-api-provider-openstack#1371

Don't merge before kubernetes-sigs/cluster-api-provider-openstack#1390 !
/hold

[k8s-ci-robot]

Welcome @lentzi90!

It looks like this is your first PR to kubernetes/test-infra 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/test-infra has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @lentzi90. Thanks for your PR.

I'm waiting for a kubernetes 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.

Details

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.

[jichenjc]

/ok-to-test

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

[jichenjc]

/lgtm

[lentzi90]

/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90, mdbooth

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/jobs/kubernetes-sigs/cluster-api-provider-openstack/OWNERS [mdbooth]

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

[k8s-ci-robot]

@lentzi90: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key cluster-api-provider-openstack-presubmits.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-openstack/cluster-api-provider-openstack-presubmits.yaml

Details

In response to this:

This adds a job for "e2e full" (similar to what CAPI has) and makes the default e2e focus on PR-Blocking tests (again similar to CAPI).

The point it not to change the behavior of current tests, but to allow adding more tests that doesn't need to run all the time.

x-ref:

• Tag current tests as PR-Blocking: 🌱 Tag current e2e tests as PR-Blocking kubernetes-sigs/cluster-api-provider-openstack#1390
• Add more e2e tests that would be part of the e2e full: 🌱 Add e2e clusterctl upgrade tests kubernetes-sigs/cluster-api-provider-openstack#1371

Don't merge before kubernetes-sigs/cluster-api-provider-openstack#1390 !
/hold

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.