-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
Preflight Checklist
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
- I am not looking for support or already pursued the available support channels without success.
- I agree to follow the Code of Conduct.
Operator Version
1.23.4
Installation Type
Official Helm chart
Bank-Vaults Version
No response
Kubernetes Version
1.34
Kubernetes Distribution/Provisioner
Digital Ocean
Expected Behavior
Audience field set as per configuration provided
Actual Behavior
Audience field remains empty and no error logs in vault-configurer and vault-operator
Steps To Reproduce
- Deploy vault-operator
- Configure vault with the following config (https://github.com/bank-vaults/vault-operator/blob/v1.23.4/deploy/examples/cr-oidc.yaml#L106)
- vault images used:
hashicorp/vault:1.18.3,hashicorp/vault:1.20.3
Configuration
externalConfig:
- roles:
- bound_audiences:
- system:konnectivity-server
bound_service_account_names:
- store
bound_service_account_namespaces:
- prod
name: store
policies: store
ttl: 1h
type: kubernetesLogs
Additional Information
I understand that the example configuration is provided for jwt auth method, but since it is quite the same as kubernetes, am I right that it should work for kubernetes as well? Or, I'm missing something?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.