Kubernetes

Exploring ArgoCD ApplicationSet at Zapier and contributor experience

This post explores the issue of blocked rolling updates during continuous deployment to Kubernetes Statefulsets due to failed volume attach attempts. It talks about workarounds and solutions for this issue, which results in consistent and faster STS rolling update times.

Currently, nginx-ingress controller can be run as a ClusterIP type service, however, it does not allow publishing this service’s endpoints to associated ingress objects. As a result, external-dns is not able to detect these ingress objects without any IP Address to create/update A DNS records for them. Why? Many may argue that why will someone need DNS records for ingress objects using ClusterIP type nginx-ingress service. They aren’t reachable from outside the kubernetes cluster, anyways....

This post will run you through how to setup an environment Atomic apps on CentOS 7, by hand. For quickstart, you can just run the Vagrantfile at here. Setup Install dependencies # yum install docker atomic kubernetes etcd Configure docker storage pool Assuming that you have a new volume: /dev/vdb attached to your machine, configure /etc/sysconfig/docker-storage-setup as below: # cat <<EOF > /etc/sysconfig/docker-storage-setup DEVS=/dev/vdb VG=docker-vg EOF Start and enable Docker # systemctl start docker # systemctl enable docker You can run # docker info to check the new specs for docker storage pool....