New at ayedo: hands-on IT workshops for Cloud Native, Kubernetes and DevOps
Hands-on ayedo workshops on Kubernetes, Docker, GitOps, security and Polycrate: small groups, prepared cloud labs, online or on site.
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.
1222 posts
Backups Are Not Recovery: How to Run a Restore Test That Works
A practical seven-step restore drill for PostgreSQL, S3 and Kubernetes, with RPO/RTO measurements, failure modes and a checklist.
Understanding Kubernetes, not just using it: ayedo now offers hands-on IT workshops
Technological independence starts with your own expertise. ayedo offers hands-on workshops on Kubernetes, Docker, GitOps and Polycrate for IT teams.
Calculating Cloud Costs Accurately: What Does an Application Really Cost?
Compare cloud offerings fairly: total cost of ownership, compute, storage, traffic, operational costs, a worked example and a checklist.
Kubernetes is moving from cgroup v1 to v2
What the move to cgroup v2 means for cluster management, resource isolation, and operations — and why Europe needs consistent infrastructure standards.
Authentik Federation in Practice: Undocumented Behavior in Sources, Groups, and Enrollment
A field report on federating two Authentik instances via OIDC: undocumented behavior in group sync, source enrollment, expression policies and login flows – with concrete patterns that work instead.
Building the Edge — Part 8
The beginning of a platform – why every architecture eventually reaches the point where it must rethink the network.
Building the Edge — Part 7
Good platforms are not built by adding more infrastructure – they are built through clearly defined responsibilities.
Building the Edge — Part 6
A connection is not yet an HTTP request – why modern edge platforms begin much earlier than many architecture diagrams suggest.
Building the Edge — Part 5
Compute is not the platform – why modern applications today consist of two platforms.
Building the Edge — Part 4
Why high availability starts in the network today – failures are not an exceptional state, but an architectural principle.
Building the Edge — Part 3
One IP address can exist in three places at once – why Anycast is not a feature, but a property of the internet.
Building the Edge — Part 2
The internet does not know applications – why BGP does not try to find the fastest path.
Kubernetes 1.38: What we know so far
Kubernetes 1.38 is targeted for December 2026. Here is what is emerging for the release and which milestones matter.
Digital Sovereignty Does Not End at the Data Center
An application can be fully operated in Germany and still rely on US infrastructure for every single access.
DNS, Routing, Anycast: Why Europe's Cloud Also Needs Its Own Edge
We recently introduced the ayedo Edge Cloud, a European edge infrastructure for DNS, Anycast, load balancing, web application firewall, DDoS protection, and controlled access to applications.
Building the Edge — Part 1
The underestimated architecture of modern applications – why modern applications no longer begin in the data center.
TLS Certificates for Public Kubernetes Endpoints
TLS for Kubernetes does not necessarily end at the Ingress. Central TLS termination at the ayedo Edge Cloud simplifies certificate management, WAF integration, and traffic control. However, additional encryption up to the cluster protects further network segments. The right decision depends on trust boundaries, operating model, compliance, and desired fault isolation.
DNS Automation for Kubernetes Behind the Edge Cloud
Kubernetes DNS and public name resolution address different challenges. Cluster resources are aware of services, ingresses, and workloads; the Edge Cloud manages public endpoints, DNS zones, and backend forwarding. A resilient operational model separates these responsibilities but automates their handovers through clearly defined interfaces.
Operating Load Balancers for Kubernetes Independently of Providers
A Kubernetes Service of type `LoadBalancer` often ties public access to the respective cloud or infrastructure provider. An independent edge layer separates this responsibility from the cluster: routing, protection, TLS, and accessibility are centrally organized, while Kubernetes can be operated at ayedo or another provider. This reduces provider dependencies and simplifies multi-cloud architectures.
Securely Accessing the Kubernetes API Server Over the Edge
A publicly accessible Kubernetes API server doesn't need to allow direct internet access to its backend address. A preceding edge layer can handle routing, TLS, DDoS protection, and backend cloaking. The key remains the separation between public accessibility, cryptographic authentication, and actual authorization within the cluster.
Ingress and Edge Cloud: Clearly Separating Responsibilities
Kubernetes Ingress and Edge Cloud serve different purposes. The Edge Cloud controls the public entry point, protects applications, and terminates TLS. In contrast, Kubernetes Ingress describes the routing within the cluster. A clear separation prevents duplicate rules, contradictory security configurations, and complex operational states.
Making Security Decisions at the Edge Transparent
Edge Security Monitoring reveals how protective measures impact public traffic. Traffic and usage statistics help operationally assess WAF rules, DDoS protection, and exposed endpoints. However, they do not fully explain individual attacks nor replace logs, traces, and application-centric security telemetry.
Multi-Cloud Security with Centralized Edge Architecture
Multi-Cloud Security often fails not due to a lack of protective features, but because of its distributed implementation. A centralized edge architecture consolidates public access, WAF, DDoS protection, TLS termination, and routing in front of heterogeneous backends. Provider independence, an autonomous system, and active-active operation reduce control and dependency points.