Deploying to kubernetes, DevOps, developers and cicd pipelines

1

Kubernetes

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.

#Developer Tools #DevOps Tools #Containers As A Service 357 social mentions

2

Medium

As for the devs. With helm they will only need to worry about a single yaml file the .vaules. And as long as you template everything you can easily teach them how to set it up. If you streamline everything, you can set the globals for most everything then have them worry about service specifics like the configmap. Make sure you make use of stuff like external services for things hosted outside of k8s. https://medium.com/@ManagedKube/kubernetes-access-external-services-e4fd643e5097 This makes the devs life even easier. They never need to worry about endpoints, the infra team handles all of that.

#Blogging #Blogging Platform #CMS 2549 social mentions

Even better, just use kustomize, which is already installed everywhere (kubectl -k).

#Development #Management #Tool 58 social mentions

4

Garden.io

They should use a higher level tool such as devspace, okteto, tilt, skaffold, garden.io, telepresence etc.

#DevOps Tools #Developer Tools #Kubernetes 22 social mentions