zookeeper-operator

zookeeper-operator copied to clipboard

Currently, if an `AuthenticationClass` is set, the client access is encrypted and requires authentication. This is not exposed in the discovery ConfigMap to be picked up by other operators to...

maltesander

nightkr

Currently this is hard-coded in the operator, which prevents us from deploying multiple instances of the chart into the same cluster, or using an alternate Helm release name to avoid...

nightkr

Active-Active Zookeeper Operator Deployment

4

Hello, is it possible to run two instances of the zookeeper operator? I didn't find an option to activate some sort of leader election. Many operators use some sort of...

hikhvar

> failure is officially deprecated/unmaintained | Details | | | ------------------- | ---------------------------------------------- | | Status | unmaintained | | Package | `failure` | | Version | `0.1.8` | |...

github-actions[bot]

> Potential segfault in `localtime_r` invocations | Details | | | ------------------- | ---------------------------------------------- | | Package | `chrono` | | Version | `0.4.19` | | URL | [https://github.com/chronotope/chrono/issues/499](https://github.com/chronotope/chrono/issues/499) |...

github-actions[bot]

Replace upstream "FIPS mode" with more fine-grained TLS hostname verification options

1

https://github.com/stackabletech/zookeeper-operator/issues/760 was closed now that FIPS mode is on by default, disabling all ZK-specific TLS verification. That's a pretty blunt tool, so we opened https://github.com/apache/zookeeper/pull/2173 to add a more fine-grained...

nightkr

Currently we only have the guide that has to serve double duty.

nightkr

Broken out from #760

nightkr

Came up in https://github.com/stackabletech/zookeeper-operator/pull/799#discussion_r1615542352 We should have status conditions (similar to ZookeeperCluster) on the Znode, e.g. if the ZNode has been created.

sbernauer