This blog post provides insight into our latest project: building the platform necessary to operate and maintain our new managed services. The platform integrates multiple tools for monitoring and secrets management, all deployed on AWS cloud infrastructure. Our goal was to establish a fully descriptive setup, leveraging Infrastructure as Code (IaC) and Continuous Deployment (CD), enabling a comprehensive GitOps approach to set up and manage the platform. Platform overview Our services platform is designed to monitor and manage our new managed service offerings.

You can't make an omelette without breaking eggs - and this also applies to the construction of our services. But what happens if we are not thorough enough when it comes to decommissioning? We regularly create JFrog instances dynamically for the development of our service and also dismantle them after testing. The process is automated using Terraform, Crossplane and it's been deployed on Kubernetes. However, one small but crucial point has been overlooked: the deletion of all associated DNS entries.

Welcome to the second blog post about our new 4DIdentity service. In the first blog post, we reviewed our motivation to create this internal service and its architecture. Brief summary: We use it to enable single sign-on for internal applications and future managed services. 4DIdentity is based on the Amazon Cognito service from AWS. We consciously chose to run it completely serverless, highly resilient, fully manageable and built using Infrastructure as Code (IaC).

In this blog post series, we want to give you a sneak peek into how we develop and maintain our applications. We have recently developed an internal service called 4DIdentity. This service acts as our central identity provider for internally used tools like ArgoCD and HashiCorp Vault. We also plan to use it in our future managed service offerings, so stay tuned! When developing the 4DIdentity service, we leveraged a set of best practices.

KubeCon Paris 2024: Train The KubeCon 2024 in Paris was, after 2019 Barcelona and 2022 in Valencia, our third attendance at the CloudNativeCon. We were very excited to hear that the KubeCon would be in Paris, finally a destination that can be easily reached by train. It seems we were not the only ones who liked the idea of taking the train instead of the airplane to travel to the KubeCon.