Polycrate CLI 0.29.14 released: Backup & Endpoint Fixes

With version 0.29.14, we have implemented two important bug fixes in the Polycrate Operator that significantly enhance the reliability of backup schedule synchronization and endpoint monitoring.

BackupSchedule K8sCluster UUID Fix

The BackupSchedule Controller previously sent a null UUID to the API, resulting in the following error:

Failed to create backup schedule in API
error: "Invalid pk \"00000000-0000-0000-0000-000000000000\""

With this fix, backup schedules are now correctly synchronized with the registered cluster ID.

Endpoint TLS Default Fix

A subtle bug caused HTTP-only endpoints to be mistakenly treated as HTTPS:

spec:
  protocol: http
  remote_port: 80
  tls: true  # ← Wrong!

The Operator then made https://example.com:80/ requests, leading to 404 errors. This issue is now resolved—if the API does not provide spec.http, TLS is correctly set to false.

→ Full Release Notes

polycrate-operator Block

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

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

Update Now

polycrate update 0.29.14

Or download the binaries directly from PolyHub.

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