Friday sept. 13th the small conference ‘Kubernetes Community Day 2019’ took place in Pakhuis de Zwijger in Amsterdam. Small-scale events like this are a nice counter-balance to the massive scale of CNCF/KubeCon: No flying for miles. Just one track so no need to choose and no missing out on interesting talks.
From what I understood this was one of the goals: Being a smaller, more accessible (both geographically and financially), more environmentally conscious addition to the big conferences. This goal was emphasized by paying attention to the global footprint by offering single-track catering as well: All vegetarian.
- Uses a combination of Terraform and Ansible for infra provisioning. Ansible more or less providing the magic & glueing.
- Uses Rancher to create clusters in different clouds, providing an identical interface for, say, Azure and GKE. (Interesting, as Terraform provides infra-as-code, but not this level of abstraction)
- Managing the operators: Operator Lifecycle Manager
- Mind permissions. What can an operator do? Who can use it?
- 3-stage pipeline: Application, Docker image & Cloud delivery
- Uses Fortify for secure coding scan
- OPA (Kubernetes)
- Sentinel (Terraform)
- Uses self-developed tool Shipper for rollouts. Multi-cluster, multi-region, multi-cloud.
- A GitOps operator.
- Doesn’t use tiller. Uses helm template.
- True hybrid cloud: Azure Stack. Use case: Installing Azure on remote location DCs where bandwith is limited, while at the same time providing a uniform interface with the ‘real’ cloud.
- Deploys artifact for every branch. Question from public: Just that service? Full stack of related services? Interesting subject.
# logs for containers that are already gone kubectl logs -p -c # CLI cluster management interface k9s # debugging helm helm template helm install --debug --dry-run helm get <release>
- Istio is not going to solve your ‘service mess’
- ‘Edge’ (What is ‘edge’ anyway?) Kubernetes projects: Kind, K3S
- Crossplane - Cloud-agnostic service catalogue (‘Give me a HA Postgres DB’, instead of ‘Give me a RDS cluster’)