Bump sigs.k8s.io/e2e-framework from 0.0.6 to 0.3.0

[dependabot]

Bumps sigs.k8s.io/e2e-framework from 0.0.6 to 0.3.0.

Release notes

Sourced from sigs.k8s.io/e2e-framework's releases.

v0.3.0

This is the third release of the 2023 after nearly four months of active contribution from the community. This release packs a great deal of interesting features, fixes, and documentation updates. Let's highlight some of them below.

Thread Safe Test Context

When Parallel test features where enabled and integrated into the framework, it was enabled with room for running into race conditions. In this release we have included changes that helps us mitigate these issues when the tests are being run in parallel. This has been achieved by doing the following mechanism.

1. Populate the test context via the BeforeEachTest handler
2. Generate a child context from the parent context and provide that for individual tests/assessments
3. Discard the context from step 2 after the tests are done
4. Pass the original parent context to the AfterEachTest handler

As part of the said changes to mitigate the race condition, we also extended the Environment.Test and Environment.TestInParallel function to return a context.Context back after the execution of the tests have been completed. This also allows for better debugging of test context to analyze failures better with the added advantage that this is not breaking any of the existing contracts. However, if you are using a golint infra and have errcheck linter enabled, you will have to make a few changes to your code to account for the newly returned value from the Environment.Test and Environment.TestInParallel functions.

Limitations

1. The Finish phase will only be able to see the context from the Setup phase and not the one from the features themselves.

Related Issues

1. kubernetes-sigs/e2e-framework#216
2. kubernetes-sigs/e2e-framework#258

Related Pull Requests

1. kubernetes-sigs/e2e-framework#292

Continubutors

@​phisco @​maruina

FluxCD Integration

e2e-framework has had helm workflow integrated under the third_party support package for a while and now, we are adding FluxCD to that arsenal. With this integration, now you can integrate your e2e tests to run against a repository using fluxcd constructs. The supported features include the following.

1. Install FluxCD components onto your cluster
2. Create and Delete GitRepository resource
3. Create and Delete Kustomization resource

Related Pull Requests

1. kubernetes-sigs/e2e-framework#255
2. kubernetes-sigs/e2e-framework#283

Contributors

@​matrus2

kwok Integration as a Cluster Provider

By default, e2e-framework has two ways to run tests. One could bring up a new cluster using kind and run the e2e tests against them using the framework or integrate against a real cluster and run tests against them. In this release, kwok is being added to that list of supported cluster providers.

... (truncated)

Commits

• 2ac6076 Merge pull request #306 from kubernetes-sigs/dependabot/github_actions/gorele...
• a47896f Bump goreleaser/goreleaser-action from 4.3.0 to 4.4.0
• f02afba Merge pull request #305 from kubernetes-sigs/dependabot/github_actions/action...
• fdad64b Bump actions/setup-go from 4.0.1 to 4.1.0
• 24332eb Merge pull request #304 from kubernetes-sigs/dependabot/go_modules/sigs.k8s.i...
• f1c6ac8 Bump sigs.k8s.io/controller-runtime from 0.15.0 to 0.15.1
• 1af0fd6 Merge pull request #255 from matrus2/flux
• c5714bb Merge pull request #298 from harshanarayana/feature/enable-issue-tempaltes
• ba50b27 Merge pull request #246 from harshanarayana/cluster-provider-interface-defini...
• 5fa0a64 Merge pull request #292 from phisco/fix/tParallel-passing-almost-everywhere
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign msherif1234 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[dependabot]

Looks like sigs.k8s.io/e2e-framework is up-to-date now, so this is no longer needed.

[openshift-merge-robot]

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.