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

Add E2E Conformance tests using k8s ci artifacts #315

Merged
merged 3 commits into from Feb 25, 2022
Merged

Add E2E Conformance tests using k8s ci artifacts #315

merged 3 commits into from Feb 25, 2022

Conversation

cpanato
Copy link
Member

@cpanato cpanato commented Feb 21, 2022

What this PR does / why we need it:

/kind feature

  • update CAPI to release v1.1.2
  • update ccm to deployment and add tolerations for 1.24+ k8s
  • Add E2E Conformance tests using k8s ci artifacts

if this we can test the head of k/k and make sure we are compliant

need new prow job: kubernetes/test-infra#25351
/hold for all tests

/assign @timoreimann @MorrisLaw @prksu

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
n/a
Special notes for your reviewer:

Documentation:

Release note:

Add E2E Conformance tests using k8s ci artifacts

Signed-off-by: Carlos Panato <ctadeu@gmail.com>
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Feb 21, 2022
@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

will need to cherry pick to release-1.1 branch

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 21, 2022
@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato

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:

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 21, 2022
@timoreimann
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 21, 2022
@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

/test ls

@k8s-ci-robot
Copy link

@cpanato: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test pull-cluster-api-provider-digitalocean-build
  • /test pull-cluster-api-provider-digitalocean-e2e
  • /test pull-cluster-api-provider-digitalocean-lint
  • /test pull-cluster-api-provider-digitalocean-test
  • /test pull-cluster-api-provider-digitalocean-verify

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-provider-digitalocean-capi-e2e
  • /test pull-cluster-api-provider-digitalocean-capi-e2e-experimental
  • /test pull-cluster-api-provider-digitalocean-conformance
  • /test pull-cluster-api-provider-digitalocean-conformance-ci-artifacts
  • /test pull-cluster-api-provider-digitalocean-e2e-workload-upgrade

Use /test all to run the following jobs that were automatically triggered:

  • pull-cluster-api-provider-digitalocean-build
  • pull-cluster-api-provider-digitalocean-e2e
  • pull-cluster-api-provider-digitalocean-lint
  • pull-cluster-api-provider-digitalocean-test
  • pull-cluster-api-provider-digitalocean-verify

In response to this:

/test ls

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.

@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

/test pull-cluster-api-provider-digitalocean-capi-e2e

@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

/test pull-cluster-api-provider-digitalocean-conformance-ci-artifacts

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 21, 2022
@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

/test pull-cluster-api-provider-digitalocean-conformance-ci-artifacts

Signed-off-by: Carlos Panato <ctadeu@gmail.com>
@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

/test pull-cluster-api-provider-digitalocean-conformance-ci-artifacts

@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

/test pull-cluster-api-provider-digitalocean-conformance

@cpanato
Copy link
Member Author

cpanato commented Feb 21, 2022

@timoreimann need the lgtm again :)

the new job is working :)
will cherry pick for the release 1.1 branch

@timoreimann
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 24, 2022
@cpanato
Copy link
Member Author

cpanato commented Feb 25, 2022

/unhold

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 25, 2022
@cpanato
Copy link
Member Author

cpanato commented Feb 25, 2022

/cherry-pick release-1.1

@cpanato
Copy link
Member Author

cpanato commented Feb 25, 2022

humm not enabled, will check how to enable

@k8s-ci-robot k8s-ci-robot merged commit 53b7d00 into kubernetes-sigs:main Feb 25, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.1.0 milestone Feb 25, 2022
@cpanato cpanato deleted the ci-conformance branch February 25, 2022 11:19
@cpanato
Copy link
Member Author

cpanato commented Feb 25, 2022

/cherry-pick release-1.1

@k8s-infra-cherrypick-robot

@cpanato: cannot checkout release-1.1: error checking out release-1.1: exit status 1. output: error: pathspec 'release-1.1' did not match any file(s) known to git

In response to this:

/cherry-pick release-1.1

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.

@cpanato
Copy link
Member Author

cpanato commented Feb 25, 2022

ahh good :) we did not release 1.1 yet 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants