// the find
spring-cloud/spring-cloud-kubernetes
Kubernetes integration with Spring Cloud Discovery Client, Configuration, etc...
Spring Cloud Kubernetes bridges the Spring Cloud programming model (service discovery, config, load balancing) with Kubernetes-native primitives like Services, ConfigMaps, and Secrets. It's for teams that want to use Spring's `@Value` and `DiscoveryClient` abstractions without rewriting their apps to speak Kubernetes directly. Active, official Spring project with a large user base.
Config reload via Kubernetes watch events is genuinely useful — your app picks up ConfigMap changes without a restart. The dual-client support (fabric8 and official Java client) gives you a real choice instead of being locked in. Integration tests run against actual Kubernetes clusters via kind, not mocks, so the test suite actually catches what it claims to catch. The config watcher and discovery server are deployable as standalone components, which means you can use them without running the full Spring Cloud stack on every pod.
No AOT or GraalVM native image support — this is explicitly called out in the README as missing, which is a real problem in 2026 when native Spring Boot is mainstream. The fabric8 vs. official client split means you have two code paths for everything, and bugs often appear in one but not the other; you'll need to know which one you're running. ConfigMap-to-property mapping is finnicky with multi-namespace setups and the namespace resolution rules are non-obvious enough that they have their own dedicated doc page. The abstraction layer sometimes fights Kubernetes — service discovery through Spring's DiscoveryClient works until you need Kubernetes-specific behavior (topology-aware routing, headless services), at which point you end up bypassing the abstraction anyway.