Does anyone have this working where you have more than one Bitbucket server (HA), and how did you deal with helm PersistentVolumeClaim?
The other idea I am thinking of is using one Helm release per Bitbucket instance on Kubernetes to get around this problem. This may even give me the option to upgrade one at a time or take one down when needed rather than using a rolling update that can go wrong and take down all the HA servers.
Any ideas/tips/examples?
@Mark Hubers of course it is possible to scale Bitbucket StatefulSet to as many replicas as you need. What issues with a PVC do you face?
The 2nd instance stays in pending mode as it says the PVC is used by another pod. I have to setup the PVC outside of helm so that we can use EBS-CSI with snapshots and to never lose that data if someone delete the PVC.
I pass this to helm:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Shared home PVC must be RWX, yours is RWO - that's why the second pod can't mount it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The shared home is RWX and that one is getting mounted on the 2nd pod. It is the local home that is RWO, as each bitbucket pod needs its own.
bitbucket-sharedhome-pv 2Gi RWX Retain Bound bitbucket/bitbucket-sharedhome-pvc efs-sc 47h
pvc-c24e8df7-3b7d-4e98-95b6-8c2a4df18b35 20Gi RWO Delete Bound bitbucket/bitbucket-localhome-pvc ebs
I cannot find a way to give each bitbuket pod it own localhome using ebs-csi driver
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Or should I even care if the localhome gets deleted at times as I not clear what happens to things like cache data etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/bitbucket/values.yaml#L223 you need to set this to true which will enable volumeClaimTemplates in Bitbucket sts spec.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.