🏪 UDS Artifactory Zarf Package

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

Pre-requisites

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

Important

NOTE: Many features are locked behind a license. Some notable features include:

• In place upgrades
• Single sign-on capabilities

Artifactory 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 ARTIFACTORY_DB_ENDPOINT Zarf var.
• This database can be logged into via the username configured with the Zarf var ARTIFACTORY_DB_USERNAME. Default is artifactory.artifactory
• This database instance has a psql database created matching what is defined in the Zarf var ARTIFACTORY_DB_NAME. Default is artifactorydb
• The user has read/write access to the above mentioned database
• Create artifactory-postgres service in artifactory namespace that points to the psql database
• Create artifactory-postgres secret in artifactory namespace with the key password that contains the password to the user for the psql database

Flavors

Flavor	Description	Example Creation
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!

Redeploying/Upgrading pre-existing Artifactory

Important

NOTE: If admin credentials are changed or different from what is generated in the artifactory-admin-credentials secret, in the values/common.yaml set:

artifactory:
  admin:
    secret: ""
    dataKey: ""

The credentials will be reset to what is in the secret if not set to empty or might break the deployment/upgrade entirely.

Contributing

Please see the CONTRIBUTING.md