Database Secret Engine
KubeVault lets you enable and configure Database Secret Engine. You can create Secret containing the Database credentials and also create RBAC Role and RoleBinding.
Enable and Configure Secret Engine
Secrets Engines are components which store, generate, or encrypt data. Secrets Engines are incredibly flexible, so it is easiest to think about them in terms of their function. Secrets Engines are provided with some set of data, they take some action on that data, and they return a result. KubeVault lets you enable & configure Database Secret Engine in a Kubernetes native way. You can use MySQL, PostgreSQL, Elasticsearch & MongoDB Secret Engines with KubeVault.
Role
In a Secret Engine, a role describes an identity with a set of permissions, groups, or policies you want to attach to a user of the Secret Engine. KubeVault operator lets you create Database Role in a Secret Engine.
Secret Access Request
A SecretAccessRequest is a Kubernetes CustomResourceDefinition (CRD) which allows a user to request a Vault server for credentials in a Kubernetes native way. A SecretAccessRequest can be created under Database Role that can be enabled in a SecretEngine. KubeVault operator lets you manage your DB user privileges with dynamic secrets rather than hard-coded credentials using SecretAccessRequest. This means that services that need to access a database no longer need to hardcode credentials.
Secret Role Binding
A SecretRoleBinding is a Kubernetes CustomResourceDefinition (CRD) which allows a user to bind a set of roles to a set of users. Using the SecretRoleBinding it’s possible to bind Database Role to Kubernetes ServiceAccounts. This way is more machine friendly and convenient for running your application with specific permissions.
