Polycrate API 0.11.20 released: LoadBalancer Fix + Debug
Polycrate API 0.11.20 fixes a JavaScript error and adds debug logging for empty timeline data.
Blog
Cloud-Native Insights & Expertise
Discover our latest articles about cloud-native technologies, Kubernetes, DevOps, and modern software development. From practical tutorials to in-depth analyses.
Latest Blog Posts
Stay up to date with our latest articles about cloud-native technologies, Kubernetes, and DevOps.
1210 posts
Polycrate API 0.11.20 fixes a JavaScript error and adds debug logging for empty timeline data.
Polycrate API 0.11.19 displays Storage & Objects directly in the S3 Bucket overview and introduces consistent bar charts for timeline data.
Polycrate API 0.11.18 fixes the timezone.utc error and changes Timeline charts to Bar-Chart style.
Polycrate API 0.11.16 addresses critical bugs: S3 Buckets are now created correctly and LoadBalancer metrics display realistic values.
AWS ElastiCache and KeyDB address the same need: extremely fast in-memory data storage for caching, queues, sessions, and real-time access. In architecture diagrams, both are often drawn as interchangeable components. This assumption falls short.
Kubernetes clusters should not be managed manually or with fragile scripts. While AWS CodePipeline tries to enforce deployments through external commands ("Push"), Flux turns this model around. As a native Kubernetes controller, Flux pulls the desired state directly from Git or OCI repositories ("Pull"). The result is a self-healing system that keeps infrastructure and applications in sync without requiring external CI servers to access the cluster.
Modern software development requires more than just code hosting. While hyperscalers like AWS attempt to lock developers into their platforms with a fragmented chain of individual services (CodeCommit, CodeBuild, CodePipeline), GitLab follows the 'Single Application' approach. It combines Source Code Management (SCM), CI/CD, Security Scanning, and Package Registry into a single, coherent interface. This reduces complexity, accelerates feedback loops, and ensures that your intellectual property (the code) and processes remain portable.
Classic browser-based tracking ('Client-Side') is dying. Browser restrictions (ITP), AdBlockers, and GDPR make data collection unreliable and legally risky. Server-Side Tagging (SST) shifts the logic from the user's device to a dedicated server. This gives companies full control back: Data is cleansed before being sent to third parties (Google, Meta), and website performance increases massively. Running GTM Server-Side in your own cluster transforms tracking from a security risk into a controlled data stream.
PDF generation is often a technical debt in modern web development. Outdated tools like wkhtmltopdf are no longer maintained, and embedding headless browsers in application containers unnecessarily bloats them and creates security vulnerabilities. Gotenberg radically solves this problem: it encapsulates the complexity of Chromium and LibreOffice in a stateless API. Instead of painstakingly building PDF logic into every microservice, delegate the task to a central, scalable service that converts HTML, Markdown, and Office documents with pixel-perfect precision.
In modern distributed systems, it's no longer enough to just know if a server is up or down. You need to understand *why* it's slow. While AWS CloudWatch provides a solid view of the infrastructure, visibility often ends at the cloud boundary. Grafana breaks through these silos. It acts as a universal visualization layer, unifying data from hundreds of sources (Prometheus, SQL, logs, traces) into a single interface. Those who use Grafana gain true end-to-end observability, regardless of where the data resides.
Polycrate API 0.11.15 resolves the last collectstatic error by removing unused KaTeX fonts.
Polycrate API 0.11.14 fixes certificate sync errors and collectstatic issues for stable production environments.
Polycrate API 0.11.13 addresses critical collectstatic issues that arose after 0.11.12.
Polycrate API 0.11.12 introduces the Milkdown Editor with @Mentions, S3 Media Storage, V2 Table Filter, and significant performance improvements.
The classic SaaS model is simple: one cloud, one architecture, all customers share the resources. However, as a SaaS provider becomes more successful in the enterprise segment, a phrase is often heard in sales conversations: "We love your software, but for compliance reasons, the data must reside in our own Azure tenant (or on-premise)."
In the growth phase of a SaaS company, there is a dangerous curve: the **Cost of Goods Sold (COGS)**. As user numbers increase, cloud costs often explode disproportionately. The reason: inefficient resource allocation, unused "zombie" instances, and lack of cost transparency per customer (Unit Economics).
Amazon Web Services is putting the "AWS European Sovereign Cloud" into operation in Brandenburg. Cloud campuses are being established in Baruth/Mark and Finsterwalde, initially through leased data centers, prospectively with their own infrastructure. Operations are carried out via a German GmbH, the data centers are located exclusively in the EU, and the staff employed are resident in Europe. The claim is clearly formulated: operation, control, and responsibility are to be entirely European.
Polycrate API 0.11.11 delivers massive performance improvements by removing the discovery phase and optimizing activity tracking.
Polycrate API 0.11.10 addresses UI bugs and performance issues in the endpoint monitoring system.
Polycrate CLI 0.29.9 introduces a redesign of Agent Health data and the submission of Check Results to the API for faster status updates.
Polycrate API 0.11.7 corrects the string representation of host objects.
Polycrate API 0.11.6 fixes UniqueValidator errors in K8sApp and Host updates that blocked the operator.
Polycrate CLI 0.29.8 enhances API error diagnosis: All 42 API client functions now display the response body on errors.
Polycrate CLI 0.29.7 addresses API schema incompatibilities and enhances error diagnostics for the operator.