<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iac on Build. Run. Repeat.</title><link>https://buildrunrepeat.com/tags/iac/</link><description>Recent content in Iac on Build. Run. Repeat.</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 01 Nov 2024 09:00:00 -0400</lastBuildDate><atom:link href="https://buildrunrepeat.com/tags/iac/index.xml" rel="self" type="application/rss+xml"/><item><title>MinIO on vSphere - Automated Deployment and Onboarding</title><link>https://buildrunrepeat.com/posts/minio-on-vsphere-automated-deployment-and-onboarding/</link><pubDate>Fri, 01 Nov 2024 09:00:00 -0400</pubDate><guid>https://buildrunrepeat.com/posts/minio-on-vsphere-automated-deployment-and-onboarding/</guid><description>&lt;p&gt;In the world of Kubernetes, reliable S3-compliant object storage is essential for tasks like storing backups. However, not everyone has access to a native S3-compatible solution, and setting one up can feel like a daunting task. MinIO, an open-source object storage solution, is a popular choice to fill this gap. Its lightweight, high-performance architecture makes it an excellent option for Kubernetes users seeking quick and reliable storage.&lt;/p&gt;
&lt;p&gt;MinIO is also one of the most widely adopted open-source object storage solutions, thanks to its simplicity and S3 compatibility. It’s perfect for Kubernetes environments that need a reliable and scalable storage layer for backups, logs, or other data.&lt;/p&gt;</description></item><item><title>Harbor Registry – Automating LDAP/S Configuration – Part 2</title><link>https://buildrunrepeat.com/posts/harbor-registry-automating-ldap-configuration-part-2/</link><pubDate>Sun, 01 Jan 2023 09:00:00 -0400</pubDate><guid>https://buildrunrepeat.com/posts/harbor-registry-automating-ldap-configuration-part-2/</guid><description>&lt;p&gt;This post continues our two-part series on automating LDAP configuration for Harbor Registry. In the &lt;a href="https://buildrunrepeat.com/posts/harbor-registry-automating-ldap-configuration-part-1/"&gt;previous post&lt;/a&gt;, we demonstrated how to achieve this using Ansible, running externally. However, external automation has its challenges, such as firewall restrictions or limited API access in some cases/environments.&lt;/p&gt;
&lt;p&gt;Note: make sure you review the previous post as it provides a lot of additional background and clarifications on this process, LDAPS configuration, and more.&lt;/p&gt;
&lt;p&gt;Here, we explore an alternative approach using Terraform, running the automation directly inside the Kubernetes cluster hosting Harbor.
This method leverages native Kubernetes scheduling capabilities for running the configuration job in a fully declarative approach and does not require any network access to Harbor from the machine running the job.&lt;/p&gt;</description></item></channel></rss>