Search for a command to run...
Articles tagged with #aks
In a scenario where you have multiple services running in one cluster, you will want them to communicate with each other. There are multiple ways to approach interservice communication; pubsub channel (like Redis), queues/topics (like RabbitMQ or Azu...
The last step in our cluster creation process -- creating an ingress controller. Let's talk about what that is. Ingress means "going in". In the K8s scenario, this means traffic going into the cluster. Egress, the anytonym of ingress, means going out...
In this short article I want to prepare us for what will be the last step in this series - ingress controller and TLS termination. This preparation will entail generating an SSL certificate and key on our local machine and storing them in a 'secret' ...
A service makes pods accessible. If you want the pods in your deployment to communicate with other pods or be accessible from outside the cluster, you must define a service. There are 4 types of services, but the two we're interested in are ClusterIP...
Now that our namespaces and resource quotas are set, it's time to finally start putting some microservices into the cluster. The way a service gets up into the cluster is via two main paths: Pod and Deployment. In YAML, you can define a pod, tell it ...
We don't want a rogue microservice to eat up all the CPU and memory in the cluster. Pods can be restricted to use a specific % of CPU and a flat amount of memory. They can be restricted either individually or at namespace level. Pods are individual ...