You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I know the current Micronaut-Kubernetes integration cannot deal with reading/parsing configmaps/secrets from mounted-volumes that have the same name.
I don't think there is a way to deal with this issue.
@Value("${username}") will just return the data of the last one parsed. The same goes for configmaps. A proposed fix could be to include the folder of the mountPath like @Value("${secret1.username}")
Another issue I have discover is that if the configmap or secret "key" starts with a numerical value it will also be ignored.
While preparing for next major release, this issue should be discussed again since it will most probably require breaking change on how the secrets are processed.
As far as I know the current Micronaut-Kubernetes integration cannot deal with reading/parsing configmaps/secrets from mounted-volumes that have the same name.
Example:
I don't think there is a way to deal with this issue.
@Value("${username}")
will just return the data of the last one parsed. The same goes for configmaps. A proposed fix could be to include the folder of the mountPath like@Value("${secret1.username}")
Another issue I have discover is that if the configmap or secret "key" starts with a numerical value it will also be ignored.
Example
@Value("${c07efbea-e85b-4026-90f9-55e40175b16f}")
will work but@Value("${8d26bd90-7f74-4a08-9fc4-5a5feb61331e }")
will not.The text was updated successfully, but these errors were encountered: