Challenge 20: one to bind them allIn Kubernetes, you can use Role-Based Access Control to restrict how the Kubernetes API can be consumed.Sep 27, 2024Sep 27, 2024
Challenge 19: tied upIn Kubernetes, there are two probes that have long-lasting implications for app availability: liveness and readiness probes.Aug 30, 2024Aug 30, 2024
Challenge 18: dead or aliveAn application receives a stream of events and publishes those in Kafka broker for further processing.Aug 23, 2024A response icon1Aug 23, 2024A response icon1
Challenge 17: Sticky messYou can configure your ingress controller to support sticky sessions.Aug 9, 2024Aug 9, 2024
Challenge 16: ThrottledCPU limits in Kubernetes are not always obvious and can lead to a spike in latency.Aug 2, 2024Aug 2, 2024
Challenge 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 12, 2024Jul 12, 2024
Challenge 14: bounceKubernetes Services: they don’t always work as you might think.Jun 21, 2024Jun 21, 2024
Challenge 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 19, 2024A response icon1Apr 19, 2024A response icon1
Challenge 12: rollin’In Kubernetes, you often use a Deployment object to create Pods.Apr 12, 2024Apr 12, 2024
Kubernetes challenge 11: going indieIn Kubernetes, you can configure three probes for your workloads: startup, liveness and readiness.Mar 29, 2024Mar 29, 2024
