Skip to content

Releases: operator-framework/java-operator-sdk

4.1.1

08 Nov 08:56
cd27711
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.1.0...v4.1.1

4.1.0

31 Oct 09:13
114c431
Compare
Choose a tag to compare

What's Changed

  • This release covers some common cases for dependent resources that was not covered yet:

    • Support multiple dependent resource of same type (#1175)
    • Support bulk dependent resources (#1182)
    • Support dependent resources with explicit state (#1221)
  • Now it is possible to configure better whether an operator should stop in case of error in event sources on startup (#1405)

    • This is also related the an added configuration for cache sync timeouts (#1318)

To see the full Changelog: v4.0.3...v4.1.0

See also the related milestone: https://github.com/java-operator-sdk/java-operator-sdk/milestone/4?closed=1

4.0.3

24 Oct 13:27
662979a
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.0.2...v4.0.3

3.2.4

21 Oct 08:03
dfae8d5
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.2.3...v3.2.4

4.0.2

19 Oct 13:34
d3e870a
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.0.1...v4.0.2

3.2.3

30 Sep 14:17
9bb3f07
Compare
Choose a tag to compare

What's Changed

  • chore: use s01 server which should be less prone to timeouts by @metacosm in #1486
  • fix: use class name to ensure we always get a non-null name by @metacosm in #1489
  • Revert "chore: use s01 server which should be less prone to timeouts (#1486)" by @csviri in #1498
  • feat: enable configuring a handler to listen to informers stopping by @metacosm in #1493

Full Changelog: v3.2.2...v3.2.3

4.0.1

26 Sep 18:48
85f420d
Compare
Choose a tag to compare

What's Changed

  • fix: only release BOM if main release succeeded by @metacosm in #1470
  • chore(deps): bump log4j.version from 2.18.0 to 2.19.0 by @dependabot in #1477
  • chore(deps): bump maven-jar-plugin from 3.2.2 to 3.3.0 by @dependabot in #1478
  • docs: fix reconciliation max interval and related issues by @csviri in #1480
  • fix: config service override executor service concurrent reconciliation numbers by @csviri in #1484
  • chore: use s01 server which should be less prone to timeouts by @metacosm in #1487
  • fix: use class name to ensure we always get a non-null name by @metacosm in #1488
  • docs: javadoc for CRUDNoGCKubernetesDependentResource by @csviri in #1483
  • chore(deps): bump junit-bom from 5.9.0 to 5.9.1 by @dependabot in #1492
  • fix: max reconciliation interval applies after retry exhaustion by @csviri in #1491
  • chore(deps): bump actions/stale from 5 to 6 by @dependabot in #1494
  • Try to get lease namespace if unspecified by @honnix in #1450
  • fix: remove problematic leader election unit test by @csviri in #1496
  • fix: concurrency issue with workflow cleanup executor by @csviri in #1495
  • Revert "chore: use s01 server which should be less prone to timeouts (#1487)" by @csviri in #1497

Full Changelog: v4.0.0...v4.0.1

3.2.2

19 Sep 15:10
c62fc73
Compare
Choose a tag to compare

What's Changed

  • fix: only release BOM if main release succeeded by @metacosm in #1471
  • fix: config service override executor service concurrent reconciliation numbers (v3) by @csviri in #1485

Full Changelog: v3.2.1...v3.2.2

4.0.0

16 Sep 08:10
b45dc88
Compare
Choose a tag to compare

This release is essentially equivalent to 3.2.0 and should be used instead of it.

We decided to re-release 3.2.0 as 4.0.0 to reflect the fact that the upgrade to Fabric8 Kubernetes Client 6.1.1 is most likely a breaking change for many projects event though the API of the Java Operator SDK itself didn't change. Migration is fairly easy to do, though, and we encourage folks to migrate to this new version since it provides many improvements, while Fabric8 client 5.x will now only receive important bug fixes. For migration information, please see: https://github.com/fabric8io/kubernetes-client/blob/v6.0.0/doc/MIGRATION-v6.md

What's Changed

Full Changelog: v3.2.0...v4.0.0

3.2.1

15 Sep 15:43
Compare
Choose a tag to compare

⚠️ This release reverts the upgrade made in 3.2.0 to Fabric8 Client 6.1. ⚠️

3.2.0 should not be used anymore and will be superseded by a future 4.0.0 release. If you wish to keep using version 6.x of the Fabric8 Kubernetes Client, please use the upcoming 4.0.0 release.

Moving forward, future developments will happen on the 4.x line and the 3.x line of releases will only receive fixes for existing users, keeping the compatibility with version 5 of the Fabric8 client. We encourage users to migrate to version 4.0.0 of the Java Operator SDK as soon as possible.

What's Changed

Full Changelog: v3.2.0...v3.2.1