Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
garden
Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
Today, I learned how to deploy a web application and mongo db to a k8s cluster by creating yaml files. If I compare the pipeline files we create in our existing cicd vs the yaml files I created today, the yaml content is a little intimidating. I mean, it was easy because I copied them from kubernetes.io. There were elements or attributes in the yaml file that intimidated me today like configMapKeyRef, selector, kind, apiVersion(2 different values apps/v1 and v1). Currently at work, our developers are the ones who create their projects, build their project and deploy their project. Most of the time, they don't even ask us anymore. They only ask us when their instance is failing to deploy. Most of the time, it's because of health check on a tcp port is wrong.
Doing this correctly is an emerging area and requires a lot of skill. There are emerging tools to help, though (see e.g. kratix https://github.com/syntasso/kratix).
They should use a higher level tool such as devspace, okteto, tilt, skaffold, garden.io, telepresence etc.