NOTE that in the following instructions it is left to the user to manage, backup and restore the vault installation once it has been installed.
For production workloads we recommend you use a cloud provider secret store or Vault as a service. Managing on-premises vault instances is undifferentiated heavy lifting that should be outsourced to a cloud provider if you can.
The prerequisites are the same as regular on-premises kubernetes around having a kubernetes cluster with ingress and storage
The difference is for vault:
- if the above button does not work then please Login to GitHub first and then retry the button
make sure you have a recent helmfile binary installed on your
setup the Vault instance in your cluster. From inside a git clone of the git repository you have just created above run the following:
jx secret vault port-forward&
jx secret vault wait
if that succeeds you should have a vault instance running in the
find out what your ingress domain is for your cluster then modify the
jx-requirements.ymlfile and modify the
verify your cluster does not already have an nginx installation. If it does then please remove the
nginxline from your
helmfile.yamlfile and remove the
helmfiles/nginxfiles. If you are using a custom nginx installation then you will need to figure out your domain by hand and won’t be able to let Jenkins X detect the load balancer IP from its included nginx installation.
git add, commit and push your changes:
git add *
git commit -a -m "fix: added domain"
git push origin master
- ensure you are connected to your cluster so you can run the following kubectl commands
kubectl get ns
kubectl get node
Install the git operator from inside a git clone of the git repository you created above.
switch to the
jx ns jx
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.