![what is kubernetes infrastructure what is kubernetes infrastructure](https://finopsinpractice.org/wp-content/uploads/2021/05/How-to-optimize-IT-costs-in-a-Kubernetes-infrastructure-1024x523.jpg)
Securing and firewalling services and their network access both inbound and outboundĪutomatically destroy and re-create failing services, pods, etc.Įxpose services allowed to be exposed to the internet securely Manage and route traffic to clusters of services Scale disks upwards in size as necessary (via Volume Autoscaler)
#WHAT IS KUBERNETES INFRASTRUCTURE CODE#
Perform gradual deployments routing selective (eg: tester) traffic to new versions of code while leaving the public on old versions of untested code Zero-downtime deploy services with blue/green or canary deployments (via an decent ingress controller (Nginx ingress, traefik, kong, ambassador, etc) Gather metrics on every, single, thing that happens on your cluster or with your services (via Prometheus)
![what is kubernetes infrastructure what is kubernetes infrastructure](https://files.helpdocs.io/kw8ldg1itf/articles/hmza5cvxib/1596228945876/image.png)
Kubernetes can do things like.Īutoscaling to add new (server) nodes to the clusterĪutoscaling your services to give them more resources (cpu/ram/disk) Kubernetes does SO much and is so foundational to success, without Kubernetes you'd need to do/setup a lot of these things manually or with your cloud provider. Then, managed SaaS services came along (eg Managed DBs, Logs, etc) that we all depend on also considered infrastructure. Then, cloud providers came along, and now we accept that a "VM" is now considered infrastructure. From an "older" point of view, only a physical server you rack in your colo is infrastructure. You really have to think of things a bit more broadly and evolve your definition over time, as it sounds like you're stuck on the old concept of infrastructure. I agree it is 100% considered infrastructure.