Skip to content

server-zd v0.1.20

Choose a tag to compare

@longquanzheng longquanzheng released this 06 Nov 08:56
e4eab0a

Breaking Changes

  • dev and local default to 32 partitions (#1306).
    • dex-server-zd dev, dex-server-zd local, and dexcli dev now create new data directories with 32 partitions instead of 1024. serve keeps 1024.
    • A data directory created by server-zd before v0.1.20 or dexcli before 1.37.0 has 1024 partitions. That includes every existing dexcli dev state directory at $HOME/.dex/zd/<port>. Starting on such a directory now fails, and the error names the directory and both counts.
    • To keep the directory, add this to the --config file (with dexcli dev, the --zd-config file):
      cluster:
        partitionCount: 1024
      Or delete the data directory; the next start creates it with 32 partitions.
    • A dev or local --config that sets commit.applierLanes above 32 without cluster.partitionCount now fails with an error that explains the new default.
    • Downgrade: to open a 32-partition directory with an older server-zd or dexcli, set cluster.partitionCount: 32.
  • dev reads api.listen from --config (#1294). Without --listen, dev and local now use api.listen from the --config file when it is set, else 127.0.0.1:8801. Previously dev ignored api.listen. dexcli dev always passes --listen and is unaffected. Do not copy the whole example configuration into an overrides file: it sets api.listen: 0.0.0.0:8801 and lease.duration: 10s.

server-zd v0.1.20

Features

  • New dex-server-zd local command for single-node production on local disk (#1294). It runs the embedded s3local object store on --data-dir with the same flags, data directory layout, and lock as dev, so a data directory can move between the two commands. local keeps the 30 s Step attempt drain of serve instead of the 2 s dev drain.
  • dev and local log a startup warning when they listen on a non-loopback address without authenticators.
  • A cluster partition-count mismatch is now a typed error that reports both counts, for serve as well. A hot standby classifies it as a configuration error.

Upgrade

  • Stop every old process, including standbys, then start v0.1.20.
  • Before server-zd 1.0, rolling a node back to an older 0.x binary after a newer one has run is not supported.

Artifacts

  • Container image dex-server-zd:0.1.20 for linux/arm64 and linux/amd64.
  • dex-server-zd binaries for Linux amd64, Linux arm64 (glibc 2.28 or newer), macOS arm64 and macOS amd64, with checksums.txt.