The kubernetes store supports reading specific secrets using a selector with the secret's name.
And the secret can be referenced in parameters:
Load secrets from multiple Kubernetes secrets by defining multiple Kubernetes secret stores with the appropriate selectors for the secrets to read:
Note: This method requires the Kubernetes service account, which is running the spiced pod, to have extended roles for secrets API access. Configure this service account with the necessary permissions to read secrets from the Kubernetes API.
Example of Kubernetes role configuration for a custom service account: