Polycrate API 0.11.10 released: Endpoint Monitoring Fixes
ayedo Redaktion 1 Minute Lesezeit

Polycrate API 0.11.10 released: Endpoint Monitoring Fixes

Polycrate API 0.11.10 addresses UI bugs and performance issues in the endpoint monitoring system.
polycrate kubernetes api endpoint-monitoring bugfix

Polycrate API version 0.11.10 addresses several UI bugs and performance issues in the endpoint monitoring system.

Highlights

  • Agent Detail Lazy Loading - Monitored Endpoints Table with pagination for improved performance
  • Agent Capacity Logic Fix - max_endpoints now uses SystemConfig instead of the outdated effective_capacity
  • VictoriaMetrics Query Optimization - Corrected query step from 30s to 60s
  • Agent Info Box Cleanup - Removed redundant and erroneous fields
  • Ingress Discovery Disabled - Operator is the single source of truth

Agent Capacity Fix

The max_endpoints property used the old effective_capacity field, which is no longer updated. This led to incorrect capacity calculations. Now, the SystemConfig value is used directly (default: 300 endpoints per agent).

Ingress Discovery

API-side endpoint discovery has been disabled. The Polycrate Operator is now the sole source for endpoint discovery. This prevents duplicate endpoints with different API IDs.

Full Release Notes

polycrate-api Block 0.5.14

The polycrate-api block has been updated to version 0.5.14:

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

Update Now

docker pull cargo.ayedo.cloud/polycrate/polycrate-api:0.11.10

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

Ähnliche Artikel