Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

util: allow configuring VAULT_BACKEND for Vault connection #2307

Merged
merged 1 commit into from Jul 22, 2021

Conversation

nixpanic
Copy link
Collaborator

It seems that the version of the key/value engine can not always be
detected for Hashicorp Vault. In certain cases, it is required to
configure the VAULT_BACKEND (or vaultBackend) option so that a
successful connection to the service can be made.

The kv-v2 is the current default for development deployments of
Hashicorp Vault (what we use for automated testing). Production
deployments default to version 1 for now.


Show available bot commands

These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

  • /retest ci/centos/<job-name>: retest the <job-name> after unrelated
    failure (please report the failure too!)
  • /retest all: run this in case the CentOS CI failed to start/report any test
    progress or results

@nixpanic nixpanic added enhancement New feature or request component/rbd Issues related to RBD component/util Utility functions shared between CephFS and RBD labels Jul 20, 2021
humblec
humblec previously approved these changes Jul 20, 2021
@nixpanic
Copy link
Collaborator Author

/retest ci/centos/upgrade-tests-cephfs

@humblec humblec added this to the release-3.4.0 milestone Jul 20, 2021
Madhu-1
Madhu-1 previously approved these changes Jul 21, 2021
@Madhu-1
Copy link
Collaborator

Madhu-1 commented Jul 21, 2021

@Mergifyio rebase

@nixpanic nixpanic force-pushed the rbd/encryption/VAULT_BACKEND branch from a0fe391 to 870a624 Compare July 21, 2021 07:12
@mergify
Copy link
Contributor

mergify bot commented Jul 21, 2021

Command rebase: success

Branch already up to date

@mergify mergify bot dismissed stale reviews from humblec and Madhu-1 July 21, 2021 07:12

Pull request has been modified.

@nixpanic
Copy link
Collaborator Author

@humblec @Madhu-1, it seems Mergify dropped the approvals here 😞

@nixpanic nixpanic requested review from humblec and Madhu-1 July 21, 2021 13:41
@nixpanic
Copy link
Collaborator Author

@Mergifyio rebase

It seems that the version of the key/value engine can not always be
detected for Hashicorp Vault. In certain cases, it is required to
configure the `VAULT_BACKEND` (or `vaultBackend`) option so that a
successful connection to the service can be made.

The `kv-v2` is the current default for development deployments of
Hashicorp Vault (what we use for automated testing). Production
deployments default to version 1 for now.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
@nixpanic nixpanic force-pushed the rbd/encryption/VAULT_BACKEND branch from 870a624 to e3fb2ea Compare July 22, 2021 09:16
@mergify
Copy link
Contributor

mergify bot commented Jul 22, 2021

Command rebase: success

Branch has been successfully rebased

@nixpanic
Copy link
Collaborator Author

/retest ci/centos/mini-e2e-helm/k8s-1.19

@nixpanic
Copy link
Collaborator Author

/retest ci/centos/mini-e2e-helm/k8s-1.19

Failed with #2264

@mergify mergify bot merged commit 82557e3 into ceph:devel Jul 22, 2021
@nixpanic
Copy link
Collaborator Author

@Mergifyio backport release-v3.3

@mergify
Copy link
Contributor

mergify bot commented Aug 10, 2021

Command backport release-v3.3: success

Backports have been created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/rbd Issues related to RBD component/util Utility functions shared between CephFS and RBD enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants