Having trouble getting clustering working for bitbucket.
Running with Bigbang, istio is the service mesh, and matallb is the load balancer
Helm Chart Version 1.16.6
Bitbucket Application Version: 8.5.0
Helm chart Values:
values:
image:
repository: docker.io/atlassian/bitbucket
tag: "8.5.0"
serviceAccount:
clusterRole:
create: true
clusterRoleBinding:
create: true
database:
type: "postgresql"
url: "jdbc:postgresql://modbucket-postgres-postgresql:5432/bitbucket"
driver: "org.postgresql.Driver"
credentials:
secretName: atlassian-postgresdb
usernameSecretKey: postgres-user
passwordSecretKey: postgresql-password
bitbucket:
clustering:
enabled: true
hazelcastService:
enabled: true
additionalEnvironmentVariables:
- name: "http_proxy"
value: "REDACTED"
- name: "https_proxy"
value: "REDACTED"
- name: "no_proxy"
value: "REDACTED"
additionalJvmArgs:
- -Dcom.redhat.fips=false
- -Djava.net.preferIPv4Stack=true
- -Datlassian.dev.mode=false
- -Datlassian.plugins.enable.wait=300
ingress:
nginx: false
# Disable SSL Configuration as Istio Ingress Controller will provide SSL configuration
# If this is "true" then default Bitbucket security configuraitons will prevent web page resolution
https: false
monitoring:
exposeJmxMetrics: true
jmxExporterImageRepo: docker.io/bitnami/jmx-exporter
podAnnotations:
traffic.sidecar.istio.io/excludeOutboundPorts: "80,443"
podLabels:
app: modbucket
volumes:
localHome:
persistentVolumeClaim:
create: true
resources:
requests:
storage: 10Gi
mountPath: "/var/atlassian/application-data/bitbucket"
sharedHome:
nfsPermissionFixer:
imageRepo: docker.io/library/alpine
imageTag: 3.18.2
persistentVolumeClaim:
storageClassName: ceph-filesystem
create: true
resources:
requests:
storage: 10Gi
mountPath: "/var/atlassian/application-data/shared-home"
The issue I am experiencing is that the Scaled Nodes:
1) The additional nodes don't show up under the webpage/admin/clustering
2) logs have the error Node authentication failed: Unexpected bytes from remote node, closing socket
I will post the logs as a reply
