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

Init container config-templating failing due to permission issue while restoring the backup from velero #431

Open
3 tasks done
smarimus opened this issue Apr 12, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@smarimus
Copy link

smarimus commented Apr 12, 2024

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.21.2

Installation Type

Official Helm chart

Bank-Vaults Version

No response

Kubernetes Version

1.25.9

Kubernetes Distribution/Provisioner

RKE2

Expected Behavior

I'm backing up the vault resource and restoring using velero and restic.

The backup operation is successful
The restore operation is giving the below exception.

`λ k logs vault-0 config-templating

time="2024-04-12T19:09:02Z" level=fatal msg="error writing template file "/vault/config/vault.json": open /vault/config/vault.json: permission denied"`

Actual Behavior

Should be able to restore the backup from velero.
Looks like there's no option to provide security context.

InitContainers: withVaultInitContainers(v, []corev1.Container{

Steps To Reproduce

No response

Configuration

No response

Logs

λ k logs vault-0 config-templating

time="2024-04-12T19:09:02Z" level=fatal msg="error writing template file \"/vault/config/vault.json\": open /vault/config/vault.json: permission denied"

Additional Information

No response

@smarimus smarimus added the kind/bug Categorizes issue or PR as related to a bug. label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant