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,
kubectl
Easily and rapidly switch between kubectl namespaces.
Career
I work with Azure a lot. And as a Solutions Architect, I often find myself seeking answers to rather deep questions, refreshing my memory on old tech or concepts, or seeking new technology or solutions to solve my problems. I admit, it's extremely hard to keep up. Whatever
Kubernetes
A few quick and easy ways to switch contexts rapidly.
Kubernetes
Logically isolate and group objects inside of Kubernetes with loose coupling.
git
There are several out there, and a lot of opinions to go with them. Having served in a consulting capacity for many organizations, ranging from small startups to very large enterprises, I have seen all of the major strategies. I've even seen organizations make up their own strategies
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
DevSecOps
The term "Pipelines as Code" means that you are defining the process through which your code moves from source control, all the way to running in production. This practice is absolutely necessary if you want to build a high performing development process that allows your system to be
culture
In my career, I have worked across so many types of companies. (List not in order) * A large tech company * A large non-profit * A small non-profit * An early-stage tech startup * A small boot-strapped Azure and DevOps consultancy * A medium-sized venture-backed Microsoft-focused consultancy * A publicly traded consultancy that focuses on Government
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.
Azure Kubernetes Service
I implemented the Azure Active Directory (AAD) integration with Azure Kubernetes Service (AKS) for Role Based Access Control (RBAC) today in an existing cluster. I use Terraform to manage the cluster as well as all of the Helm installs and custom resource definitions that I apply via kubectl. The Problem