🏪 UDS Jira Zarf Package

This package is designed to be deployed on UDS Core, and is based on the upstream Jira chart.

Pre-requisites

The Jira Package expects to be deployed on top of UDS Core with the dependencies listed below being configured prior to deployment.

Jira is configured by default to assume the internal dependencies that are used for testing (see postgres in the bundle).

Database

• A Postgres database is running on port 5432 and accessible to the cluster via the JIRA_DB_ENDPOINT Zarf var.
• This database can be logged into via the username & password given in the postgre connection secret (see values/common-values.yaml).
• This database instance has a psql database created matching what is defined in the Zarf var JIRA_DB_NAME. Default is jiradb
• The user has read/write access to the above mentioned database
• Create jira-postgres service in jira namespace that points to the psql database
• Create jira-postgres secret in jira namespace with the key password that contains the password to the user for the psql database

Flavors

Flavor	Description	Example Creation
upstream	Uses images from docker.io within the package.	zarf package create . -f upstream
registry1	Uses images from registry1.dso.mil within the package.	zarf package create . -f registry1

Important

NOTE: To create the registry1 flavor you will need to be logged into Iron Bank - you can find instructions on how to do this in the Big Bang Zarf Tutorial.

Releases

The released packages can be found in ghcr.

UDS Tasks (for local dev and CI)

*For local dev, this requires you install uds-cli

Tip

To get a list of tasks to run you can use uds run --list!

Contributing

Please see the CONTRIBUTING.md