Got different teams running Java/springboot in my workplace to move their docker file image k8s setup to standardized @Paketo_io build packs. we can use customize builders per team while ensuring standard workflow with security patches.
@cnunciato Ease of managing complex stacks, used component resources and custom logic to handle stateful resources. Would have been verbose/not straight forward in TF.
@aantn I would gather metrics/telemetry of the queue, scale with KEDA and HPA based on queue items. The other option is to watch the queue and handle deploy using a separate daemon/deploy script.
Came across kubectl client side throttling due to multiple API GET requests when using Cluster API.
This led me down the rabbit hole to Discovery cache (client) and how it supports variation of k8s resources.
Things I learnt this week
- Bootstrapping using kubeadm and cluster provisioners like cluster API, Crossplane etc will soon catch up/cross other IaaC tools.
- Tilt is nice for local/prod k8s microsvc dev
- Finalizers tweak can cleanup Cluster API resources too