Speaker: Kingdon Barrett, OSS Engineer, Weaveworks Outside of work, Priyanka enjoys hanging out with her husband and two rescue dogs as well as traveling around the globe. She was instrumental in the multi-tenancy migration to utilize Flux for an internal Kubernetes offering. Previously she was a software developer at a large insurance company where she was on the delivery engineering team working on GitOps enablement. She has worked on a multitude of topics including front end development, UI automation for testing and API development. Priyanka “Pinky” Ravi is a Developer Experience Engineer at Weaveworks. Jose will share insights on the many benefits of TF-Controller, then demo a common use case implementation. Priyanka provides an in-depth look at TF-controller, a Flux-based controller to reconcile your Terraform resources the GitOps Way. This enables you to take advantage of all the benefits of GitOps: streamlined and secure deployments, quicker time to market, and more time to concentrate on app development! You can rest easy knowing that your deployments are always up to date with your desired state. What if teams could ensure that what they defined in the Terraform HCL code is what is always running and available? Flux can continuously look for changes on your Terraform resources and do reconciliation with the desired state.
This means that teams won't notice a sudden change in the running environment often with critical consequences. Additionally, GitOps is in every IT roadmap, but unfortunately Terraform doesn't have an easy way to reconcile its resources. Some organizations depend heavily on their Terraform scripts because they are using multiple providers, have built wrappers around those providers, and might even be deploying their application code along with Terraform.
Reconcile Terraform Resources the GitOps Way with Priyanka Ravi
0 kommentar(er)
