I recently encountered a puzzling issue with a Nomad job, where a crucial environment variable was missing a # character.
After some investigation, I finally uncovered the root cause.
In this blog post, I highlighted how we use the IONOS Cloud LaaS solution to collect the Logs from our Nomad cluster. But how to give users access to the logs?
I've been selected to speak at SyliusCon 2025 in October. At the conference, I will talk about "Simplifying Sylius Containerization with DDEV". After having to cancel at the last minute last year, I'm thrilled to have a second opportunity to deliver this presentation, and I'm looking forward to sharing it with you.
Last year, I covered how to set up and configure the IONOS Cloud LaaS offering. Now it is time to showcase how we collect logs from Nomad via FluentBit and send them to the IONOS Cloud LaaS.
Tideways helps you optimize application performance by continuously monitoring and analyzing it.
While doing a bit of spring cleanup in the various Nomad clusters we host for us and our customers, I wanted to delete a few dynamic host volumes that were no longer in use.
For one of our customer projects, I was looking for an SFTP server. Although my Google search was unsuccessful, ChatGPT offered an interesting suggestion I had never heard of: SFTPGo.
A while ago, Nomad introduced the concept of Workload Identity to authenticate to Vault and obtain a Vault ACL token specific to the task. This way, Nomad jobs only have access to "their" own secrets, which provides an additional layer of security.
In a recent customer project, I was looking for a way to let a legacy application send emails via Office 365 or more specifically, the MS Graph API.