Sourced from testcontainers's releases.

1.16.3

What's Changed

Highlights

Testcontainers 1.16.3 includes many changes, but there are two key highlights in this release:

k3s module (#4582) @​rnorth, @​kiview

We've had plenty of feedback from users wanting to use Testcontainers to help test Kubernetes components. In particular, this is useful for people developing Kubernetes controllers/operators, who need something more than just a mocked Kubernetes API. In this release we're bringing the k3s module, which gives you a neat way to spin up the K3S lightweight Kubernetes inside of a container. We believe that k3s hits a sweet spot for ease of use and performance, so is a good option for testing Kubernetes components.

Now, launching a lightweight single-node Kubernetes cluster within your tests is easy as:

K3sContainer k3s = new K3sContainer(DockerImageName.parse("rancher/k3s:v1.21.3-k3s1"));
k3s.start();
String kubeConfigYaml = k3s.getKubeConfigYaml();
ApiClient client = Config.fromConfig(new StringReader(kubeConfigYaml));
// now use client to talk to your cluster!

Check out the docs to find out more!

Selenium 4 compatibility (#4914) @​GannaChernyshova, @​tobiasstadler, @​kiview, @​rnorth

Selenium 4 was announced a while back, but we needed to make some changes to Testcontainers' Selenium/Webdriver module for compatibility. We're happy to announce that these changes have now been made, so you can now use Selenium 4 with Testcontainers!

As part of this upgrade we have to drop compatibility with Selenium 2, but believe that this will not have any practical impact.

🚀 Features & Enhancements

• [Reusable mode] Don't log about starting container unnecessarily (#4844) @​pkubowicz
• Display Ryuk logs when it fails to start (#4842) @​vincz7777
• [couchbase] Explicitly configure service quotas (and allow customizat… (#4802) @​daschl
• removed hardcoded log level setting on mockserver (#4798) @​szymonprz
• [couchbase] Ignore transient primary index creation error. (#4681) @​daschl
• Execute Docker credential program through shell on Windows (#4763) @​mruemeli

🐛 Bug Fixes

• change external port check to it can timeout and retry (#4680) @​kmcgovern-apixio

📖 Documentation

... (truncated)

• 34cfdc8 Fix k3s for latest Docker for Mac (cgroupsv2) (#4937)
• 04937b5 Replace jcenter with mavenCentral in all examples (#4931)
• 19b58cd Use 2.8.8 compatible Jackson API (#4930)
• f7dcfa8 Use jackson 2.8.8 in k3s module (#4928)
• 631531f Merge pull request #4927 from testcontainers/combined-pr-branch
• af7cec0 Bump up Gradle Enterprise plugin dependencies (#4926)
• 0a04166 Merge remote-tracking branch 'origin/dependabot/gradle/modules/postgresql/io....
• 0ff1c79 Merge remote-tracking branch 'origin/dependabot/gradle/modules/localstack/com...
• 8186795 Basic K3S module (#4582)
• 3a16a79 Bump r2dbc-postgresql in /modules/postgresql
• Additional commits viewable in compare view

Sourced from junit-jupiter's releases.

1.16.3

What's Changed

Highlights

Testcontainers 1.16.3 includes many changes, but there are two key highlights in this release:

k3s module (#4582) @​rnorth, @​kiview

We've had plenty of feedback from users wanting to use Testcontainers to help test Kubernetes components. In particular, this is useful for people developing Kubernetes controllers/operators, who need something more than just a mocked Kubernetes API. In this release we're bringing the k3s module, which gives you a neat way to spin up the K3S lightweight Kubernetes inside of a container. We believe that k3s hits a sweet spot for ease of use and performance, so is a good option for testing Kubernetes components.

Now, launching a lightweight single-node Kubernetes cluster within your tests is easy as:

K3sContainer k3s = new K3sContainer(DockerImageName.parse("rancher/k3s:v1.21.3-k3s1"));
k3s.start();
String kubeConfigYaml = k3s.getKubeConfigYaml();
ApiClient client = Config.fromConfig(new StringReader(kubeConfigYaml));
// now use client to talk to your cluster!

Check out the docs to find out more!

Selenium 4 compatibility (#4914) @​GannaChernyshova, @​tobiasstadler, @​kiview, @​rnorth

Selenium 4 was announced a while back, but we needed to make some changes to Testcontainers' Selenium/Webdriver module for compatibility. We're happy to announce that these changes have now been made, so you can now use Selenium 4 with Testcontainers!

As part of this upgrade we have to drop compatibility with Selenium 2, but believe that this will not have any practical impact.

🚀 Features & Enhancements

• [Reusable mode] Don't log about starting container unnecessarily (#4844) @​pkubowicz
• Display Ryuk logs when it fails to start (#4842) @​vincz7777
• [couchbase] Explicitly configure service quotas (and allow customizat… (#4802) @​daschl
• removed hardcoded log level setting on mockserver (#4798) @​szymonprz
• [couchbase] Ignore transient primary index creation error. (#4681) @​daschl
• Execute Docker credential program through shell on Windows (#4763) @​mruemeli

🐛 Bug Fixes

• change external port check to it can timeout and retry (#4680) @​kmcgovern-apixio

📖 Documentation

... (truncated)

• 34cfdc8 Fix k3s for latest Docker for Mac (cgroupsv2) (#4937)
• 04937b5 Replace jcenter with mavenCentral in all examples (#4931)
• 19b58cd Use 2.8.8 compatible Jackson API (#4930)
• f7dcfa8 Use jackson 2.8.8 in k3s module (#4928)
• 631531f Merge pull request #4927 from testcontainers/combined-pr-branch
• af7cec0 Bump up Gradle Enterprise plugin dependencies (#4926)
• 0a04166 Merge remote-tracking branch 'origin/dependabot/gradle/modules/postgresql/io....
• 0ff1c79 Merge remote-tracking branch 'origin/dependabot/gradle/modules/localstack/com...
• 8186795 Basic K3S module (#4582)
• 3a16a79 Bump r2dbc-postgresql in /modules/postgresql
• Additional commits viewable in compare view

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 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)