Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
We are using a Apache-Kafka deployment on Kubernetes which is based on the ability to label pods after they have been created (see https://github.com/Yolean/kubernetes-kafka). The init container of the broker pods takes advantage of this feature to set a label on itself with its own numeric index (e.g. "0", "1", etc) as value. The label is used in the service descriptors to select exactly one pod.
This approach works fine on our DIND-Kubernetes environment. However, when tried to port the deployment onto a Docker-EE Kubernetes environment we ran into trouble because the command kubectl label pod generates a run time error which is completely misleading (also see https://github.com/fabric8io/kubernetes-client/issues/853).
Related posts
- I would like to make calls to the K8s API server from within a Java app that is running in a pod. How would I authenticate it to do so?
- Does Fabric8io K8s java client support patch() or rollingupdate() using YAML snippets?
- Using Java annotation processor in Scala
- Is 6 LPA worth it to work at a startup from 9 AM to 8 PM?
- How Netflix Uses Java