3.5.1-debian-10-r30 release
This commit is contained in:
parent
ac77d60c4f
commit
96b7322d38
|
|
@ -17,7 +17,7 @@ RUN chmod g+rwX /opt/bitnami
|
|||
COPY rootfs /
|
||||
RUN /opt/bitnami/scripts/etcd/postunpack.sh
|
||||
ENV BITNAMI_APP_NAME="etcd" \
|
||||
BITNAMI_IMAGE_VERSION="3.5.1-debian-10-r29" \
|
||||
BITNAMI_IMAGE_VERSION="3.5.1-debian-10-r30" \
|
||||
ETCDCTL_API="3"
|
||||
|
||||
EXPOSE 2379 2380
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ etcdctl_get_endpoints() {
|
|||
# POD_NAME.HEADLESS_SVC_DOMAIN.NAMESPACE.svc.cluster.local (using headless service domain)
|
||||
# 10-237-136-79.SVC_DOMAIN.NAMESPACE.svc.cluster.local (using POD's IP and service domain)
|
||||
# We need to discad the latter to avoid issues when TLS verification is enabled.
|
||||
[[ "$(getent hosts $ip)" = *"$parent_domain"* ]] && return 0
|
||||
[[ "$(getent hosts "$ip")" = *"$parent_domain"* ]] && return 0
|
||||
return 1
|
||||
}
|
||||
|
||||
|
|
@ -304,12 +304,12 @@ is_healthy_etcd_cluster() {
|
|||
if is_boolean_yes "$ETCD_DISASTER_RECOVERY"; then
|
||||
if [[ -f "/snapshots/.disaster_recovery" ]]; then
|
||||
# Remove current node from the ones that need to recover
|
||||
remove_in_file "/snapshots/.disaster_recovery" "$host:$port" || true
|
||||
remove_in_file "/snapshots/.disaster_recovery" "$host:$port"
|
||||
# Remove nodes that do not exist anymore from the ones that need to recover
|
||||
read -r -a recovery_array <<< $(tr '\n' ' ' < "/snapshots/.disaster_recovery")
|
||||
read -r -a recovery_array <<< "$(tr '\n' ' ' < "/snapshots/.disaster_recovery")"
|
||||
for r in "${recovery_array[@]}"; do
|
||||
if [[ ! " ${endpoints_array[*]} " =~ " $r " ]]; then
|
||||
remove_in_file "/snapshots/.disaster_recovery" "$r" || true
|
||||
if [[ ! "${endpoints_array[*]}" =~ $r ]]; then
|
||||
remove_in_file "/snapshots/.disaster_recovery" "$r"
|
||||
fi
|
||||
done
|
||||
if [[ $(wc -w < "/snapshots/.disaster_recovery") -eq 0 ]]; then
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ Non-root container images add an extra layer of security and are generally recom
|
|||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
||||
|
||||
|
||||
* [`3`, `3-debian-10`, `3.5.1`, `3.5.1-debian-10-r29`, `latest` (3/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-etcd/blob/3.5.1-debian-10-r29/3/debian-10/Dockerfile)
|
||||
* [`3`, `3-debian-10`, `3.5.1`, `3.5.1-debian-10-r30`, `latest` (3/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-etcd/blob/3.5.1-debian-10-r30/3/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/etcd GitHub repo](https://github.com/bitnami/bitnami-docker-etcd).
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue