Should support and default to zookeeper official image

[donbowman]

Should support and default to zookeeper official image

[donbowman]

i would recommend mounting the scripts u need as configmaps, then u can use the upstream directly.
this is how i did the helm change.
helm/charts#11343

e.g. just put the script u need in a configmap in yaml, and mount into the location u want it inside the container.

[spiegela]

Actually the Docker container file for emccorp/zookeeper is included within this repo. We should bump it to the 3.5 final, but it is required as it has several scripts used for custom startup, readiness and liveness checks.

[abh]

Putting scripts in configmaps sounds ... not great. Liveness and readiness checks might be able to fit in a sidecar (not the custom startup scripts though, most likely).

Maybe the official images will take patches to support the things we need here?

[spiegela]

Another option would be to add an initContainer that populates the /data volume with the required scripts and the zu utility. @EronWright Do you have an opinion on this?

[EronWright]

From an OSS perspective, it does seem good to use the stock image. I don't know enough about the scripts to have a strong opinion. The sidecar pattern is highly useful for liveness checks, as mentioned above. I would strive for that if possible.

[AceHack]

We would like to see this, any new thoughts on using this?

[fpj]

Note that the "official" image is not an image produced by the Apache community, see for example the "where to file issues" line:

https://github.com/31z4/zookeeper-docker/issues

[fpj]

We are also not pushing images to emccorp on docker hub, we are pushing them under pravega:

https://hub.docker.com/repository/docker/pravega/zookeeper-operator

Is this issue still valid?

[anishakj]

Closing this issue as it is invalid.