Polycrate CLI 0.29.5 Released: Wildcard Endpoint API Sync Fix

With version 0.29.5, Polycrate receives a critical bug fix: Endpoints with wildcard hostnames like *.example.com can now be correctly synchronized with the API.

The Problem

Endpoints from Ingress resources with wildcard hostnames could not be synchronized with the Polycrate API. The API rejected the name with a 400 error:

unexpected status code: 400, response: {"name":["Name doesn't match RegEx..."]}

The Cause

The operator only replaced dots with dashes during endpoint creation, but not the wildcard asterisk:

• *.saar1.s3.loopbck.io → *-saar1-s3-loopbck-io ❌

However, * is not a valid character for API names.

The Fix

The hostToName() function is now also used during API sync. This correctly converts wildcards:

• *.saar1.s3.loopbck.io → wildcard-saar1-s3-loopbck-io ✅

→ Full Release Notes

polycrate-operator Block

The polycrate-operator block has been updated to version 0.3.10:

polycrate pull cargo.ayedo.cloud/ayedo/k8s/polycrate-operator
polycrate run polycrate-operator install

Update Now

polycrate update 0.29.5

Or download the binaries directly from PolyHub.

Polycrate is ayedo’s Infrastructure-as-Code tool for declarative multi-cluster management. Learn more →