Articles Today I Learnt FM


Container ports do not have to be exposed explicitly in Kubernetes pods on

All containers that are part of a pod have the same network namespace, and (can) bind to all IPs in that namespace. Kubernetes does not offer any implicit filtering between pod network namespace and …

AWS throttles DNS requests to the VPC resolver on

At work we use CoreDNS to forward queries to the VPC resolver, as we run most of our services in Kubernetes. What that means is that we are routing all DNS queries through a few machines, and we …

Using for loops to generate lightly customized resources
Cluster autoscaler does not scale down nodes when pods have in-memory storage attached on

In some of our pods we use a temporary storage, to exchange data between the containers that belong to the same pod.

> k describe pod customersite
    Type: …
You cannot restrict pod/exec permission to subsets of pods in a namespace on

While it is possible to craft a role using wildcards in the resource names, it will not work to restrict pod/exec permissions. Let’s test this:

Let’s start with some basic RBAC rules and …

Some of the things that we routinely do on our EKS nodes
That you can impersonate pods in K8s on

Useful feature when you are developing against a cluster API is to act as the pod where your feature will be deployed.

In Kubernetes every pod is automatically assigned a service account. This is …

Two different ways to inject configuration parameters to your pods
How to include AWS-specific info when using kubectl get nodes on

The standard configuration when using kubectl get nodes is meant to be working for any cluster, therefore does not include any specific information about the K8s distribution you are using.

At work we …

Page 1