Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Clarify docs section "Using a ConfigMap PropertySource"
See original GitHub issueThe docs section at https://docs.spring.io/spring-cloud-kubernetes/docs/current/reference/html/#configmap-propertysource states
The default behavior is to create a Fabric8ConfigMapPropertySource based on a Kubernetes ConfigMap that has a metadata.name value of either the name of your Spring application (as defined by its spring.application.name property) or a custom name defined within the bootstrap.properties file under the following key: spring.cloud.kubernetes.config.name.
Can you clarify what bean gets created when usingspring-cloud-starter-kubernetes-client-config without using the Fabric8 client.
Also it is helpful to add a callout that reminds the reader that beans must be marked with @RefreshScope for hot-reload to work maybe even explain the hot reload feature works with Spring Cloud k8s.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
looks good to me.
I agree @asaikali what do you think?