namliz
commented
7 years ago Kubernetes CI CD Pipeline using Quay App Registry
Private Docker Registry in Kubernetes if we choose to self host.
Open namliz opened 7 years ago
namliz
commented
7 years ago Kubernetes CI CD Pipeline using Quay App Registry
Private Docker Registry in Kubernetes if we choose to self host.
namliz
commented
7 years ago Using Google Cloud Container Builder on a fork of this repo to the side as a temporary measure.
Manifest / Version controlled config
Bake into container # 1
Kubernetes binaries, stick to major releases for now, just reference in TF_vars for above
Overlay deployment (
kubectl apply -f {Weave, Flannel, Calico}.yml)Prometheus & Pushgateway - not currently baked anywhere, bake and specify image in TF_vars
CoreDNS / KubeDNS - former is not yet currently baked anywhere, bake and specify image in TF_vars
Terraform should generate appropriately the yaml files for all of the above and place in
/etc/kubernetes/manifests.To deploy in a sane manner we end up with a bundle, but at the same time, we want to somehow build on every subcomponent of the bundle as well. This requires multiple CI pipelines, trigger new bundle builds whenever one of the components get updated, start new clusters on every new bundle.
Additional reading:
Templates+Parameterization proposal has been stuck for a long time, no plans until after(?) 1.7. https://github.com/kubernetes/kubernetes/issues/23896#issuecomment-254844544 - "Helm and Templates are different tools and have different strengths".
Artifactory / Container Registry / Build pipeline - TBD
Trigger run on every new Terraform, provisioning files changes, overlay image, Prometheus, Demo/CI artifacts.
Process:
Input: Manifest file with all the versions and desired flags Ouput: Submitted to cncfdemo.io backend (which generates a uuid) and saved as statically hosted file Cluster deployed with uuid, pings endpoint after successful bootstrap, appends information during run
Run successfully completes on final event or times out between pings.