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 context path vs. readiness probe

Konrad Garus_ucgohw

I want to deploy Bitbucket on a context path like "/bitbucket".

I'm setting `service.contextPath=/bitbucket`. It updates `SERVER_CONTEXT_PATH` in YAML (which is great), but the readiness probe is still at "/status". As a result it's never "ready". I suspect the tests may have the same issue.

To get this to work in my setup, right now I'm using the following patch.

kubectl patch statefulset bitbucket --type='json' \
  -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe/httpGet/path", "value": "/bitbucket/status"}]'

kubectl delete pod bitbucket-0

It looks like it could be a bug in the chart.

Comments

Yevhen

@Konrad Garus can you please file an issue at https://github.com/atlassian/data-center-helm-charts?

Konrad Garus_ucgohw

I'd be happy to do it, but I don't know how.

It clearly says that Github issues is for feature requests only: https://github.com/atlassian/data-center-helm-charts/issues/new/choose

The main support form is for Atlassian products, it wants a product license (which is irrelevant here).

I created a ticket there just in case, we'll see if that works: https://getsupport.atlassian.com/servicedesk/customer/portal/35/CA-1683371

Konrad Garus_ucgohw

@Yevhen OK, that support ticket was a major failure. I don't have a product SEN and no-one will talk to me because my email is associated with a partner and I'm hitting the authorization wall.

Please let me know what exactly is the right path to submit bugs for these charts.

Yifei Zhang_1s82dx

Hi @Konrad Garus , can you please raise a Github issue, or a PR if you have a solution already, with `bug` label? We'll take care of it from there. Cheers.