jx: jx boot fails at step to create vault
Summary
jx boot fails at step to create vault
Steps to reproduce the behavior
-
changes in jx-requirements.yml
cluster: provider: eks gitKind: bitbucketcloud gitName: bc gitServer: https://bitbucket.org secretStorage: vault vault: name: clustername-vault webhook: lighthouse
-
Run
jx boot
Expected behavior
Installs Jenkins X in the EKS cluster
Actual behavior
while installing vault, jx boot errors out
vault-operator addon succesfully installed.
vault operator installed in namespace jx
finding vault 'clustername-vault' in namespace jx
Creating new system vault
error: creating vault: missing S3 bucket flag
error: failed to interpret pipeline file jenkins-x.yml: failed to run '/bin/sh -c jx step boot vault' command in directory 'systems/vault', output: ''
Jx version
The output of jx version
is:
NAME VERSION
jx 2.0.798
Kubernetes cluster v1.13.10-eks-5ac0f1
kubectl v1.16.0
git 2.21.0
Operating System "Fedora release 30 (Thirty)"
Jenkins type
- Serverless Jenkins X Pipelines (Tekton + lighthouse)
- Classic Jenkins
Kubernetes cluster
EKS created using https://eksctl.io/gitops-quickstart/setup-gitops/
Operating system / Environment
Operating System “Fedora release 30 (Thirty)”
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 8
- Comments: 15 (3 by maintainers)
The problem lies within the way we handle Vault.
We need you to provide an IAM User in order to use its access keys to authenticate the Vault pod.
You can only have a maximum of 2 access key pairs per IAM User, so you’ll have to delete one of the pairs before running boot again.
You can also provide an already existing key pair through env variables:
VAULT_AWS_ACCESS_KEY_ID and VAULT_AWS_SECRET_ACCESS_KEY.
I hope this helps.