Transit engine compatibility support
There is compatibility support for the previous versions of Ceph which used the Transit engine as a simple key store.
You can use the compat option in the Transit engine to configure the
compatibility support. You can disable previous support with the following command:
Example
[ceph: root@host03 /]# ceph config set client.rgw rgw_crypt_vault_secret_engine transit compat=0
Note: This is the default for future versions and you can use the current version for new
installations.
The normal default with the current version is:
Example
[ceph: root@host03 /]# ceph config set client.rgw rgw_crypt_vault_secret_engine transit compat=1
This enables the new engine for newly created objects and still allows the old engine to be used for the old objects. To access old and new objects, the Vault token must have both the old and new transit policies.
You can force use only the old engine with the following command:
Example
[ceph: root@host03 /]# ceph config set client.rgw rgw_crypt_vault_secret_engine transit compat=2
This mode is selected by default if the Vault ends in export/encryption-key.
Important: After configuring the
client.rgw options, you need to restart
the Ceph Object Gateway daemons for the new values to take effect.Reference
For more information, see the following: