50 posts tagged with "Devops"

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.

To have the most flexibility for our CI pipelines, we use the Docker runner in our GitLab CI environment. This allows us to easily customize each job in each build pipeline for each of our customers, ensuring they match our specific needs.

Recently, I encountered an issue with our new Nomad cluster. After adding a Nomad client node via a VPN connection, the node was successfully visible in Nomad and able to run workloads.

However, I experienced a problem with Nomad's built-in service discovery feature, which was unable to retrieve the correct IP address for a deployed service.

With the 1.10.0 release of Nomad, dynamic host volumes can now be managed without restarting a Nomad Client node to apply the configuration change.

Writing Nomad Job files isn't that hard. Once you understand the basic structure, you can quickly write job files to deploy an application on a Nomad cluster.

When setting up our first version of our internal Nomad cluster 6 years ago, we quickly realized that we also needed a secrets management solution. Vault, being another product from Hashicorp, was the natural fit for our needs.