nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BitBucket Installation Issue on Kubernetes - EKS

Himanshu Sinha_95od77

With EFS

I am trying to deploy bitbucket datacenter with cluster disabled on EKS using Helm charts. I have the EKS cluster up and running in AWS. The EKS cluster has an ingress controller, coreDns and other workloads required for this deployment. However, when I install bit bucket helm chart, the test-shared-home-permissions fail. I am using EFS as shared home. Here is the link to this test. I have the followed the documentation provided here.

With NFS

After reading different post on EFS, I thought to give a try with NFS. However, when I install bit bucket helm chart, the test-application-status fail. I am using NFS as shared home. I am able to access the NFS from another machine and it seems to work properly. Here is the link to this test. As part of the application status test, its trying to get the status of the application which its not able to get and it fails. I have the followed the documentation provided here. The bit bucket pod is always in pending status.

Comments

Yevhen_5guu4k

@Himanshu Sinha it's really difficult to say what's wrong without logs. Did you enable nfs permission fixer? I expect this init container to fail first if there are permissions issues in the volume.

By the way, EFS isn't officially supported as storage backend for Bitbucket due to performance issues.

As to NFS, I guess the app just failed to start because it wasn't able to write to shared home. Providing logs and kubectl get pods -n $namespace will help.

Dylan Rathbone

Hi @Himanshu Sinha

The fact that the application status test is not passing and the pod is in a pending state suggests that there could possibly also be something else (other than shared storage) preventing the BB pod from starting. There are a few things you should confirm first:

Ensure that all of the required prerequisites are in place.
Ensure that the values.yaml has been configured correctly based on these prerequisites.

Having done this, and after re-deploying, if the pod is still in a pending state then you can use the following command to provide additional detail as to why the pod is in this state:

kubectl describe pod <pod_name>

This should hopefully reveal what the issue is.

Dylan.

Yevhen_5guu4k

Ah, I missed that the pod is in pending state. Odds are the PVC has never been bound and the pod has unbound PVCs. Let's take a look at events in kubectl describe. I'd also look at kubectl describe pvc too.

Himanshu Sinha_95od77

nfs permission fixer is enabled. Yes, the app failed to start. It seems to be related to shared home - nfs.

Himanshu Sinha_95od77

Here is the output from kubectl describe.

From the kubectl pods output attached above, I believe all the prerequisites are in place.

Yevhen_5guu4k

@Himanshu Sinha can you please provide output from kubectl describe pod rel-test-bitbucket-0 -n bit-bucket? Events in there will shed some light