Technical guide resolves authentication conflicts between Confluent Schema Registry and MSK Serverless on EKS

A developer documented a multi-layer authentication conflict when deploying Confluent Schema Registry on EKS against an MSK Serverless cluster. The first issue involved Kubernetes injecting malformed environment variables, crashing the Schema Registry pod, which was fixed by disabling service link injection. A second problem was the Confluent base image lacking the required AWS MSK IAM authentication library for MSK Serverless. The solution required building a custom Docker image that manually adds the necessary JAR file to a specific directory.