praqma / ask

Helm and Helmsman charts for ASK. This repository is no longer being maintained. Please see main README file.

NOTICE OF DEPRECATION

If you are not yet aware. Atlassian now provides Helm charts and images for the running of their Data Center products on Kubernetes.

Therefore we will deprecate our implementation known as Atlassian Software in Kubernetes (ASK) as we believe that Atlassian is in the best position to provide a deployment model like this.

Please see Atlassian's documentation for running Data Center products on Kubernetes.

• Documentation
• Github repo

This means we will no longer update or maintain ASK repositories nor push new images to Docker Hub.

You are therefor encouraged to push any images you presently use to a registry of your choice and clone/fork this repository if needed.

Other repositories affected by this are:

• https://github.com/Praqma/jira - Jira docker image
• https://github.com/Praqma/confluence - Confluence docker image
• https://github.com/Praqma/bitbucket - Bitbucket docker image

ASK Helm Repo

This repository is a component of ASK Atlassian Software in Kubernetes. The charts are built with CircleCI and pushed into the public ASK helm repository.

These Helm charts relies on the Docker images found in these repositories :

• https://github.com/Praqma/jira
• https://github.com/Praqma/confluence
• https://github.com/Praqma/bitbucket

Helper repositories :

• https://github.com/Praqma/synchrony
• https://github.com/praqma/ask-elasticsearch

To configure the repository on your machine:

helm repo add ask https://praqma-helm-repo.s3.amazonaws.com/
helm repo update
helm search repo ask

Then, you can install charts from that repo:

helm install ask/jira

Contribution

Contributions to the charts or the the docker images are welcome through PRs! Please refer to the contribution guide for more info.

Support

For support requests, please open an issue on this repo (and tag @hoeghh) or contact [email protected]

ask's Issues

Node Discovery Jira

Hi everyone
Thanks for opensourcing your helm-charts! I used your helm-charts as a starting point and deployed Jira Data Center in our K8s-Cluster. I can scale the installation up to 2 nodes and it works as expected. But with more than 2 nodes the replication of the cache doesn't work. The nodes always appear in the list in the jira settings, also these that for some reason don't replicate. I didn't find an error pointing me to the problem. Do you have an idea what could be going wrong? Or maybe you have a tip how to better debug this issue?

Failing Check:

Cluster Index Replication
What does this check do?
Checks that the index is being replicated across the cluster in a timely fashion.
Result
Index replication for cluster node 'jira-3.jira.jira-test.svc.cluster.local' is behind by 3,405 seconds.

Thanks,
Dominik

Warning from confluence and bitbucket charts

Warning: Merging destination map for chart 'confluence'. The destination item 'MatchLabels' is a table and ignoring the source 'MatchLabels' as it has a non-table value of:

Jira incorrect readiness probe

The 'readinessProbe.httpGet' gets passed elements that belong at the 'readiness' object level.

File: https://github.com/Praqma/ask/blob/master/jira/templates/statefulset.yaml

See also https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#probe-v1-core

confluence 8091 port is not run

I set Datacenter.Enabled: true,I install confluence data center with confluence helm chart,but 8091 port is not run.
logs:
DATACENTER_MODE is set to 'true' and CONFLUENCE_DATACENTER_SHARE is found set to: /var/atlassian/confluence-datacenter/
Proceeding to setup Confluence in DataCenter mode...
The file /var/atlassian/application-data/confluence/confluence.cfg.xml was not found; because, this may be the first node - still booting up.

Error 404

Hi, those repo's are not available
https://github.com/Praqma/synchrony
https://github.com/praqma/ask-elasticsearch

Error response from daemon: pull access denied for praqma/jira, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

After installed jira helm chart, the Pod status is always as 'Waiting: ImagePullBackOff'. Looks to me the praqma/jira image either does not exist or is private.

Here is my test:

`$ docker login
Authenticating with existing credentials...
Login Succeeded

$ docker pull praqma/jira
Using default tag: latest
Error response from daemon: pull access denied for praqma/jira, repository does not exist or may require 'docker login': denied: requested access to the resource is denied`

BitBucket service should use generic 'sticky' implementation

BitBucket requires sticky sessions on the web interface. The bitbucket service have the following values in values.yaml:

Service:
Annotations:
traefik.backend.loadbalancer.sticky: "true"

This should be replaced with a 'sessionAffinity: ClientIP' on the service since this is a generic, non-traefik specific solution.

Error: release singed-seastar failed: StatefulSet.apps "singed-seastar" is invalid

Hi @hoeghh I got the following errors when trying to install jira and confluence chart to a minikube cluster. Any ideas?

$helm install ask/jira
Error: release singed-seastar failed: StatefulSet.apps "singed-seastar" is invalid: [spec.selector: Required value, spec.template.metadata.labels: Invalid value: map[string]string{"app":"singed-seastar"}: selector does not match template labels]

$helm install ask/confluence
Error: release washed-lizard failed: StatefulSet.apps "washed-lizard" is invalid: [spec.selector: Required value, spec.template.metadata.labels: Invalid value: map[string]string{"app":"washed-lizard"}: selector does not match template labels]

Environment
clientVersion: buildDate: "2019-10-15T23:41:55Z" compiler: gc gitCommit: c97fe5036ef3df2967d086711e6c0c405941e14b gitTreeState: clean gitVersion: v1.16.2 goVersion: go1.12.10 major: "1" minor: "16" platform: darwin/amd64 serverVersion: buildDate: "2019-09-18T14:27:17Z" compiler: gc gitCommit: 2bd9643cee5b3b3a5ecbd3af49d09018f0773c77 gitTreeState: clean gitVersion: v1.16.0 goVersion: go1.12.9 major: "1" minor: "16" platform: linux/amd64

$helm ls
NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE donating-joey 1 Mon Oct 21 21:42:04 2019 DEPLOYED jenkins-1.7.8 lts default singed-seastar 1 Mon Oct 21 22:01:34 2019 FAILED jira-1.0.0 default washed-lizard 1 Mon Oct 21 22:05:10 2019 FAILED confluence-1.0.0 default

Bitbucket template fails to Deploy due to missing Elasticsearch chart

I added the Praqma chart catalog to my Rancher installation.
I go to Apps-->Launch and select the Praqma Bitbucket chart
I supply a few values and then click Launch. The app fails to install with the following message:

Wait helm template failed. Error: found in requirements.yaml, but missing in charts/ directory: elasticsearch : exit status 1