GitOps for Multi-Region: Consistency through ArgoCD and Multi-Cluster Management
In a multi-region architecture, “configuration drift” is the greatest enemy of …
Polycrate CLI version 0.29.10 focuses on security, bringing comprehensive Kubernetes hardening for the Operator according to NIST SP 800-190 and CIS Benchmark.
The Operator image has been hardened according to common security standards and is now available as a rootless image by default:
Security Features:
# New Security Configuration
blocks:
- name: polycrate-operator
config:
security:
enabled: true
run_as_non_root: true
read_only_root_filesystem: true
network_policy:
enabled: trueCompliance:
The Operator now validates hostnames via DNS lookup before reporting them as endpoints to the API:
*.example.com) are automatically skippedNew shortcut command for workspace initialization:
# Instead of polycrate workspace init
polycrate init --with-name my-projectCertificates and backups are no longer displayed as “Unnamed” - the Operator now correctly reports the name to the API.
The polycrate-operator block has been updated to version 0.3.17:
polycrate pull cargo.ayedo.cloud/ayedo/k8s/polycrate-operator
polycrate run polycrate-operator installpolycrate update 0.29.10Or download the binaries directly from PolyHub.
Polycrate is ayedo’s Infrastructure-as-Code tool for declarative multi-cluster management. Learn more →
In a multi-region architecture, “configuration drift” is the greatest enemy of …
In the traditional IT world, maintenance windows are often a necessary evil. Operating system …
TL;DR Cloud independence in Kubernetes landscapes is not achieved through isolated clusters but …