MinIO, once a darling of the open-source object storage world, has followed a path we’ve seen before: slowly pulling the rug on its OSS community. It started subtly, features were stripped from the community edition, leaving users with a barebones experience. Now, MinIO has taken it a step further by ceasing distribution of pre-built binaries altogether. The project is now source-only, as confirmed in their GitHub README. This move significantly raises the barrier to entry for users who relied on the simplicity of ready-to-run binaries. One of MinIO’s biggest selling points was its sleek UI. With that gone from the OSS version and enterprise pricing remaining steep, it’s time to consider alternatives. Read more

Because I didn’t want to push all my custom images and sourcecode to public repos like hub.docker.com, I was looking for a self-hosted solution. After checking out the features of the official Docker registry, I was a bit underwhelmed by the missing repo based auth and the lack of combining the use as repository and cache. Read more

Having to log into all of your VKS clusters one by one sucks as you either have to export your vSphere Password as an environment variable (which is kinda insecure) or enter the Password for each of your Clusters over and over again. As we got annoyed with that one of my Customers (Ralf Dahmen) and I decided to fix this by developing a little bash script that automatically detects all clusters in your vSphere Namespaces and logs you in to them, to do so you only ned to enter your Password once. Read more

When using NSX-T for networking in combination with NSX ALB for load balancing in the vSphere IaaS Control Plane, the ALB Service Engines attach to each Tier-1 Router (vSphere Namespace) with one vNIC. Naturally, there’s a limit of 10 vNICs per Service Engine, meaning we can connect up to 8 Tier-1 routers to one Service Engine, as one vNIC is needed for management and another for frontend traffic. We were curious to see how NSX ALB would handle more than 8 vSphere Namespaces in this setup. My colleague Steven Schramm and I decided to test this in our lab. Read more

While I was testing Broadcom’s new Release 8.0.3, I encountered some issues getting my nested lab to work in a Proxmox environment. Despite enabling Nested Virtualization on all Proxmox nodes and setting the VM CPU type to ‘host,’ the vCLS service wouldn’t start due to EVC issues, causing DRS to malfunction. Troubleshooting Nested Virtualization First, I checked whether nested virtualization was enabled on the Proxmox nodes. This can be verified with the following command: Read more