Giant Swarm’s Top Cloud Native Posts of 2018
by Tommy Hobin on Feb 11, 2019
Our team is hard at work perfecting the ideal Kubernetes stack for you. Still, we find time to share knowledge about our experiences in the containerized world. With 2018 a near-distant memory, we’d like to take a moment to reflect on the cloud native topics that you all loved so much.
Skim through our top 10 list below and catch up on an article or two that you may have missed, or would like to revisit.
-
Using Kubernetes LoadBalancer Services on AWS by Platform Engineer, Ross Fairbanks
-
What you Yaml is What you Get by Support Engineer, Tobias Bradtke
-
Deep Dive Into Kubernetes Networking in Azure by Site Reliability Engineer, Roman Sokolkov
-
Production-grade Kubernetes Now in an Azure Region near You by Platform Engineer, Ross Fairbanks
-
Monitoring On-Demand Kubernetes Clusters with Prometheus by Platform Reliability Engineer, Joe Salisbury
-
Why Is Securing Kubernetes so Difficult? by Developer Advocate, Puja Abbassi
-
Giant Swarm Vs OpenShift by Co-Founder and CEO, Henning Lange
-
Logging Best Practices for Kubernetes using Elasticsearch, Fluent Bit and Kibana by Platform Engineer, Ross Fairbanks
-
Securing the Base Infrastructure of a Kubernetes Cluster by Developer Advocate, Puja Abbassi
-
The State of Kubernetes 2019 by Co-Founder and CCO, Oliver Thylmann
We are continuously updating our blog and Kubernetes Documentation. Follow us on Twitter or stop by our blog to get updates from our team.
You May Also Like
These Related Stories
Giant Swarm’s top 10 cloud-native hits of 2019
The Giant Swarm team is always hard at work perfecting the ideal cloud-native stack for our clients. Yet, still, we find time to share knowledge about …
Managed Cloud Native Stack - How Giant Swarm Does Cloud
A lot of us at Giant Swarm were at KubeCon in Copenhagen back in May. As well as being 3 times the size of the previous edition in Berlin the atmosphe …
How Giant Swarm Enables a New Workflow
By now we all know that Amazon AWS changed computing forever and it actually started as an internal service. The reason for the existence of AWS is pr …