Closed pshakhov closed 2 years ago
You can create ServiceAccount in advance and then use it.
You can create ServiceAccount in advance and then use it.
@CantosSong, but if ServiceAccount resource creating also deprecated in our super-secure-and-managed cluster?
serviceAccountName: our_sa
have all permissions for reading, but it seems like application/starter ignores this SA.
Why not just mount the configmap in the container and then use spring.config.import
to add the configuration? Sounds like the best approach is to not use Spring Cloud Kubernetes at all.
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
Describe the bug Now i using
implementation("org.springframework.cloud:spring-cloud-starter-kubernetes-client-config:2.1.1")
for working with configmaps. Spring boot 2.6.4. org.springframework.cloud:spring-cloud-dependencies:2021.0.1Our cluster policies declines creating rbac manifests (clusterrolebindings etc.).
If i remove clusterrolebindings manifests, application cant get configmap. But when i mount configmaps to deployment manifest and uses in bootstrap.yml paths to mounted configs (like 1st answer from https://stackoverflow.com/questions/56863782/cannot-read-configmap-with-name-xx-in-namespace-default-ignoring ), application successfully gets configmap and works with it.
But, in deployed without rbac manifests apps pod logs:
How can i use starter without explicit clusterrolebindings manifest? Unsuccessfully tried with
In
bootstrap.yml
:Mounting configmap like this:
Example: Not actual not in our infrastructure.