Releases: hazelcast/hazelcast-docker
Releases · hazelcast/hazelcast-docker
v5.4.1
Increase RHEL testing MC startup timeout [DI-435] (#908) When testing RHEL images, [the tests often fail](https://github.com/hazelcast/hazelcast-docker/actions/workflows/tag_image_push_rhel.yml), most recently because the MC pod failed to start in time: > error: timed out waiting for the condition on pods/test-13631969388-1-17-hazelcast-enterprise-mancenter-0 ``` Conditions: Type Status PodReadyToStartContainers True Initialized True Ready False ContainersReady False PodScheduled True {...} Warning Unhealthy 2m13s (x6 over 4m13s) kubelet Liveness probe failed: Get "http://10.131.0.66:8081/health": dial tcp 10.131.0.66:8081: connect: connection refused ``` I've done [lots of investigation to try to get more information](https://hazelcast.atlassian.net/browse/DI-435) without any success, but what I _have_ noticed is that even on [successful tests](https://github.com/hazelcast/hazelcast-docker/actions/runs/13631962459), we still have multiple failures before MC is up-and-running: ``` Conditions: Type Status PodReadyToStartContainers True Initialized True Ready True ContainersReady True PodScheduled True {...} Warning Unhealthy 101s (x2 over 111s) kubelet Liveness probe failed: Get "http://10.131.0.61:8081/health": dial tcp 10.131.0.61:8081: connect: connection refused ``` My _assumption_ is that the timeout is too low (in fact, the timeout doesn't make sense at all due to the flakey nature) and as such the build failures are arbitrary - which increasing the timeout _partially_ addresses. Fixes: [DI-435](https://hazelcast.atlassian.net/browse/DI-435) Post-merge actions: - [ ] backport - [ ] retag [DI-435]: https://hazelcast.atlassian.net/browse/DI-435?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
v5.3.8
Increase RHEL testing MC startup timeout [DI-435] (#908) When testing RHEL images, [the tests often fail](https://github.com/hazelcast/hazelcast-docker/actions/workflows/tag_image_push_rhel.yml), most recently because the MC pod failed to start in time: > error: timed out waiting for the condition on pods/test-13631969388-1-17-hazelcast-enterprise-mancenter-0 ``` Conditions: Type Status PodReadyToStartContainers True Initialized True Ready False ContainersReady False PodScheduled True {...} Warning Unhealthy 2m13s (x6 over 4m13s) kubelet Liveness probe failed: Get "http://10.131.0.66:8081/health": dial tcp 10.131.0.66:8081: connect: connection refused ``` I've done [lots of investigation to try to get more information](https://hazelcast.atlassian.net/browse/DI-435) without any success, but what I _have_ noticed is that even on [successful tests](https://github.com/hazelcast/hazelcast-docker/actions/runs/13631962459), we still have multiple failures before MC is up-and-running: ``` Conditions: Type Status PodReadyToStartContainers True Initialized True Ready True ContainersReady True PodScheduled True {...} Warning Unhealthy 101s (x2 over 111s) kubelet Liveness probe failed: Get "http://10.131.0.61:8081/health": dial tcp 10.131.0.61:8081: connect: connection refused ``` My _assumption_ is that the timeout is too low (in fact, the timeout doesn't make sense at all due to the flakey nature) and as such the build failures are arbitrary - which increasing the timeout _partially_ addresses. Fixes: [DI-435](https://hazelcast.atlassian.net/browse/DI-435) Post-merge actions: - [ ] backport - [ ] retag [DI-435]: https://hazelcast.atlassian.net/browse/DI-435?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
v5.5.4
Add application logs to RHEL action logging [DI-430] [5.5.4] (#906) Backports https://github.com/hazelcast/hazelcast-docker/pull/901
v5.5.0
Fix pushing tag
v5.2.5
Rename EDITIONS to RELEASE_TYPE
v5.3.6
Fix publishing EE image to RH registry [v5.3.6]
v5.2.4
Fix publishing EE image to RH registry [v5.2.4]
v5.1.7
Fix publishing EE image to RH registry [v5.1.7]
v5.0.5
Fix publishing EE image to RH registry [v5.0.5]
v5.3.5
Do not push multiple tags for DEVEL versions [v5.3.5]