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 27Sep 27
Challenge 19: tied upIn Kubernetes, there are two probes that have long-lasting implications for app availability: liveness and readiness probes.Aug 30Aug 30
Challenge 18: dead or aliveAn application receives a stream of events and publishes those in Kafka broker for further processing.Aug 231Aug 231
Challenge 17: Sticky messYou can configure your ingress controller to support sticky sessions.Aug 9Aug 9
Challenge 16: ThrottledCPU limits in Kubernetes are not always obvious and can lead to a spike in latency.Aug 2Aug 2
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 12Jul 12
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 191Apr 191
Kubernetes challenge 11: going indieIn Kubernetes, you can configure three probes for your workloads: startup, liveness and readiness.Mar 29Mar 29
