Daniele PolencicChallenge 19: tied upIn Kubernetes, there are two probes that have long-lasting implications for app availability: liveness and readiness probes.Aug 30Aug 30
Daniele PolencicChallenge 18: dead or aliveAn application receives a stream of events and publishes those in Kafka broker for further processing.Aug 231Aug 231
Daniele PolencicChallenge 17: Sticky messYou can configure your ingress controller to support sticky sessions.Aug 9Aug 9
Daniele PolencicChallenge 16: ThrottledCPU limits in Kubernetes are not always obvious and can lead to a spike in latency.Aug 2Aug 2
Daniele PolencicChallenge 15: Down the rabbit holeIn Kubernetes, you can expose your application to external traffic by using a Service of type: NodePort. When you create a NodePort…Jul 12Jul 12
Daniele PolencicChallenge 14: bounceKubernetes Services: they don’t always work as you might think.Jun 21Jun 21
Daniele PolencicChallenge 13: All you can eatIn Kubernetes, you can use limits to restrict the amount of resources, such as CPU and memory, that a container can use.Apr 19Apr 19
Daniele PolencicChallenge 12: rollin’In Kubernetes, you often use a Deployment object to create Pods.Apr 12Apr 12
Daniele PolencicKubernetes challenge 11: going indieIn Kubernetes, you can configure three probes for your workloads: startup, liveness and readiness.Mar 29Mar 29
Daniele PolencicChallenge 10: multiplying podsIn Kubernetes, you can have a single control plane to ingest API requests, schedule workloads and store resources.Mar 221Mar 221