Cloud Native Academy
Cloud Native Academy
Cloud Native Academy is on-the-job experience. It's a way to gain real-world experience through hands-on learning labs.
Cloud Native Academy
Cloud Native Academy is on-the-job experience. It's a way to gain real-world experience through hands-on learning labs.
Kubernetes
Do we really mean anything? No. Because not everything is capable of being deployed with Kubernetes, and some things are not worth deploying on Kubernetes. Those things are beyond the scope of this writing, but in a future series, we will explore the options available for getting those applications onto
Kubernetes
Explain it like I'm five: Kubernetes. Here are the big highlights that define the use case of Kubernetes.
Kubernetes
With only a single command, you could have a fully-functional cluster running locally in seconds!
terraform
Did you know that you can fully create a managed Kubernetes cluster in Azure using Terraform? Well you can take that one step further and also manage what's installed in your cluster using Terraform and Helm. This can be done by using the Helm provider for Terraform. Now,
Kubernetes
How to solve 413 Request Entity Too Large in Kubernetes using NGINX Ingress.
Kubernetes
Let's say you have a pod that you want to reject all traffic to, unless the traffic is coming from a specific type of pod. In this case, an ingress Network Policy will serve your needs. Here's a quick example of what that might look like
Kubernetes
What happens if a node joins a cluster before it is ready? Fortunately, you'll never have to find out. For this very reason, there is a test suite maintained by the Kubernetes community called the Node Conformance Test. This set of tests will ensure that the node complies
Kubernetes
The limits of Kubernetes are generally going to be difficult to hit for many organizations. But having said that, here are the major limitations of Kubernetes: * Maximum pods per node: 100 * Maximum nodes: 5,000 * Maximum pods: 150,000 * Maximum containers: 300,000
Kubernetes
A few quick and easy ways to switch contexts rapidly.
Azure Kubernetes Service
At my current company, the powers that be have bought into a multi-cluster approach. I'm not saying 1 cluster per environment or region. No. I'm saying 1 non-production and 1 production cluster per system per region. Essentially, each team gets their own pair of clusters in
azure active directory
Acronyms: * AAD - Azure Active Directory * AKS - Azure Kubernetes Service * RBAC - Role-based access control Recently, I implemented AAD for AKS RBAC. The documentation doesn't do a great job of visualizing what the mappings look like, so here's a quick view of how you can
Azure Kubernetes Service
Did you know that Terraform can run kubectl commands? Yep! There's a provider for Kubernetes. The Kubernetes provider has a growing list of resources that you can manage via Terraform. For instance, you could declaratively and explicitly manage Kubernetes permissions via Terraform by defining roles and role bindings.
Kubernetes
This is an incredibly useful tool. If you have an application running in Kubernetes and you need to connect to you application or database, you can simply forward a port to your local machine via the kubectl port-forward command. Let's say you have a MySQL database running in
Kubernetes
For teams that are looking to build out a Kubernetes cluster and migrate their applications, my first reaction is always the same, no matter the skill-level and capability of the team. Here's something of how the conversation goes: First, let's identify your Kubernetes administrators and let
Career
When getting started with Kubernetes, I was extremely lost. I tried jumping straight into the Kubernetes documentation, but I wasn't able to make sense of it all and where to begin. It's okay if that's where you are – that's totally normal. So,