Polycrate CLI 0.29.2 released: Operator Bugfixes and Self-Reference Panic Fix

With version 0.29.2, Polycrate receives an important bugfix release with corrections for the Kubernetes Operator and critical panic fixes.

Operator: Log Level is Respected

The Operator previously always used DEBUG logging, regardless of configuration. Now the --loglevel flag is correctly respected:

Operator: Metrics Use API ID

The Prometheus metrics of the Operator (polycrate_io_endpoint_id) previously used the Kubernetes UID instead of the Polycrate API ID. This led to mismatches when correlating metrics with API data.

Fix: Metrics now use status.api_id from the Endpoint CR.

→ Operator Documentation

Self-Reference Block Panic

A block with a from: stanza that referenced itself caused a panic when executing an action:

# BEFORE: Panic
- name: my-block
  from: my-block  # ← Self-reference!

Fix: Self-reference is now detected and aborted with a clear error message:

Error: block 'my-block' references itself in 'from:' stanza - circular reference not allowed

Pull/Push Alias Commands

The alias commands polycrate pull and polycrate push did not have workspace flags (-w, --workspace) registered, which led to a panic.

Fix: AddWorkspaceFlags() added to both alias commands.

Build: ldflags Corrected

The Go ldflags pointed to the wrong path, causing polycrate version to always return “latest”. Now the correct version is displayed.

→ Full Release Notes

polycrate-operator Block

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

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

Update Now

polycrate update 0.29.2

Or download the binaries directly from PolyHub.

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