Event language
UI language
In Viettel, our public cloud services are heavily based-on open source projects like OpenStack, Kubernetes, Prometheus,... For the Kubernetes related products, they were built on top of Cluster API that uses OpenStack as an infrastructure provider.<br><br>By default, the cluster that was created by Cluster API did not contain some components like ELK/EFK stack, Prometheus,... We can guide our users to manually install these components with some scripts/manifests. However, that manually process can easily introduce lots of issues to our customer.<br><br>Therefore, by leveraging the power of FluxCD and its toolkit (Helm Controller), we can provide a better solution for our customers to manage pre-defined kubernetes workloads on these clusters.<br><br>In this presentation, we will share:<br>- Using Cluster API to build a Kubernetes Services for public cloud<br>- Consideration and gotchas when using Cluster API with OpenStack<br>- How we can automation and managing workloads on multiple Kubernetes cluster with ease<br><br>[1] Cluster API is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters.<br>[2] Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories), and automating updates to configuration when there is new code to deploy.
