Downgrade psycopg2-binary to 2.8.x to avoid DATETIME column bug

Issue with psycopg2 version workaround: apache/superset#15768
Fixed in (unreleased) Superset: apache/superset#17713

docker/superset/Dockerfile

@@ -1,4 +1,5 @@
 # Based on the latest stable release
+# TODO: After this has been upgraded to 1.5.x, update psycopg2-binary below to whatever's latest
 FROM apache/superset:1.4.0
 
 # Install a selection of drivers for connecting Superset to various common database types.
@@ -7,14 +8,18 @@ FROM apache/superset:1.4.0
 # See here for full list of supported DBs and their connection strings:
 #   https://superset.apache.org/docs/connecting-to-databases/installing-database-drivers
 #
-# The listed versions are the latest found in PyPI as of the last check.
+# The listed versions are the latest found in PyPI as 2022/02, EXCEPT FOR psycopg2-binary,
+# where using latest (2.9.3 as of writing) creates problems with DATETIME columns:
+#   https://github.com/apache/superset/issues/15768
+# This is fixed in a recent Superset commit to master, but it hasn't been released yet (1.5.x?):
+#   https://github.com/apache/superset/pull/17713
 RUN pip install \
   clickhouse-driver==0.2.3 \
   clickhouse-sqlalchemy==0.1.8 \
   cockroachdb==0.3.5 \
   elasticsearch-dbapi==0.2.7 \
   mysqlclient==2.1.0 \
-  psycopg2-binary==2.9.3 \
+  psycopg2-binary==2.8.6 \
   pyhive==0.6.4 \
   redis==4.1.2 \
   sqlalchemy-trino==0.4.1

kube/deploy.sh

@@ -45,7 +45,7 @@ kubectl delete secret sh.helm.release.v1.${RELEASE_NAME}.v1 --ignore-not-found
 SETTINGS="walden_docker_org=${WALDEN_ORG:-docker.io/scienz},\
 walden_devserver_tag=${WALDEN_DEVSERVER_TAG:-${WALDEN_TAG:-2022.02.09}},\
 walden_metastore_tag=${WALDEN_METASTORE_TAG:-${WALDEN_TAG:-2022.02.08}},\
-walden_superset_tag=${WALDEN_SUPERSET_TAG:-${WALDEN_TAG:-2022.02.09}},\
+walden_superset_tag=${WALDEN_SUPERSET_TAG:-${WALDEN_TAG:-2022.02.10}},\
 walden_trino_tag=${WALDEN_TRINO_TAG:-${WALDEN_TAG:-2022.02.09}},\
 minio_replicas=${MINIO_REPLICAS:-4},\
 minio_arch=${MINIO_ARCH:-amd64}"