Skip to content

mAIndmeld 0.5.2: runner survives Kubernetes service links

Choose a tag to compare

View all tags
@dev-dull dev-dull released this 25 Sep 02:03
· 14 commits to main since this release
v0.5.2
850b8e2

Fixed

  • MAINDMELD_PORT and MAINDMELD_BIND values of the form tcp://...,
    which Kubernetes injects into every pod in a namespace with a Service
    named maindmeld, are ignored with a warning instead of crashing at
    start; the runner command no longer loads server config at all. Both
    Kubernetes Deployments set enableServiceLinks: false. Seen on the
    first cluster roll of the runner, where the runner pod crash-looped.

Images:

  • ghcr.io/dev-dull/maindmeld:0.5.2@sha256:4d8a88b942a8bc55ba6df563f557233ea77a69b89b1e6edd8ea82eb1d7a46c26
  • ghcr.io/dev-dull/maindmeld-runner:0.5.2@sha256:3f79a071a6af43fe771ecc43d6f15e03660a638e8d448b92f8bcbee9a51f52f1
Assets 2
Loading