Skip to content

Releases: jgroups-extras/jgroups-kubernetes

2.0.2.Final

13 Feb 15:08
84c2537
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.0.1.Final...2.0.2.Final

1.0.17.Final

13 Feb 14:51
e544828
Compare
Choose a tag to compare

What's Changed

  • [1.x] Sanitize log message - remove Authorization HTTP header values by @TomasHofman in #209
  • [1.x] Trivial pom scm cleanup and test deps updates. by @rhusar in #212

Full Changelog: 1.0.16.Final...1.0.17.Final

2.0.1.Final

20 Mar 12:34
f0d7860
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.0.13.Final...2.0.1.Final

1.0.16.Final

01 Sep 12:23
6cec403
Compare
Choose a tag to compare

What's new since 1.0.15.Final:

  • Fix for #124 repeating warning message on kubernetes endpoint unavailability

Thanks,
Rado

1.0.13.Final

11 Oct 10:46
Compare
Choose a tag to compare

What's new since 1.0.12.Final:

  • Fix for #75 and removal of a false-positive error message.
  • Fix for #77 that prevents from forming singleton clusters during initial discovery request. This introduces a new property for the protocol - KUBERNETES_USE_NOT_READY_ADDRESSES, which is enabled by default.

Big thanks to @rhusar for a lot of help during this release!

1.0.12.Final

01 Aug 08:03
Compare
Choose a tag to compare

What's new since 1.0.10.Final:

  • Fix for #70 Test code clean up thanks to @4fath
  • Fix for #72 Separating cluster during an upgrade thanks to @IlyaMar

Big thanks to all the contributors!
Sebastian

1.0.5.Final

30 Oct 12:25
Compare
Choose a tag to compare

As you may have noticed we skipped some versions between Beta1 and 1.0.5.Final. We have had some hiccup with the release procedure.

This version contains the following features:

  • #38 Fixed memory leak
  • #36 Split clusters during upgrade
  • #31 HTTPS is now the default protocol

Version upgrades:

  • Upgraded to JGroups 4.0.4

1.0.0.Beta1

14 Jun 11:20
Compare
Choose a tag to compare

The new 1.0.0.Beta1 release has been completely rewritten by @belaban. The main part of the work has been done within this two issues #23 and #22.

Below is a summary of changes:

  • The latest KUBE_PING doesn't require embedded HTTP server for discovery. Thus it is no longer required to expose port 8888 in Pods.
  • The number of dependencies has been decreased. Currently we only require JGroups and OAuth library.
  • The new KUBE_PING works only with JGroups 4. There will be no JGroups 3 support.
  • Some of the environmental variables were shortened and we removed OPENSHIFT prefix. So if you use OPENSHIFT_KUBE_PING_NAMESPACE, you will need to change it to KUBERNETES_NAMESPACE. Please refer to https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/README.adoc for more information.

0.9.3

23 May 13:12
Compare
Choose a tag to compare

Changelog:

  • Fixed releasing connections for embedded HTTP Server
  • Fixed JGroups 3/4 compatibility issues
  • Fixed test suite
  • Fixed Message.setSrc compatibility issues
  • Updated documentation

0.9.2

15 Mar 08:59
Compare
Choose a tag to compare

Changelog:

  • #18 Fixed JGroups 3/4 compatibility. This was a critical bug that prevented users from using 0.9.1 release with JGroups 3.6.x
  • Fixed possible NullPointerException in handlePingRequest method
  • Added token support
  • #17 Added additional tests for wrong labels