Platform One Sonarqube deployed via flux
- Minimum compute requirements for single node deployment are at LEAST 64 GB RAM and 32 virtual CPU threads (aws
m6i.8xlarge
instance type should do) - k3d installed on machine
# Download Zarf
make build/zarf
# Login to the registry
set +o history
# registry1.dso.mil (To access registry1 images needed during build time)
export REGISTRY1_USERNAME="YOUR-USERNAME-HERE"
export REGISTRY1_TOKEN="YOUR-TOKEN-HERE"
echo $REGISTRY1_TOKEN | build/zarf tools registry login registry1.dso.mil --username $REGISTRY1_USERNAME --password-stdin
set -o history
# This will run make build/all, make cluster/reset, and make deploy/all. Follow the breadcrumbs in the Makefile to see what and how its doing it.
make all
Below is an example of how to use this projects zarf package in your UDS Bundle
kind: UDSBundle
metadata:
name: example-bundle
description: An Example UDS Bundle
version: 0.0.1
architecture: amd64
packages:
# Sonarqube
- name: sonarqube
repository: ghcr.io/defenseunicorns/uds-capability/sonarqube
ref: x.x.x
The SonarQube Capability expects the database listed below to exist in the cluster before being deployed.
- Create
sonarqube
namespace - Label
sonarqube
namespace withistio-injection: enabled
- A Postgres database is running on port
5432
and accessible to the cluster - This database can be logged into via the username configured with the zarf var
SONARQUBE_DB_USERNAME
. Default issonarqube
- This database instance has a psql database created and configured with zarf var
SONARQUBE_DB_NAME
. Default issonarqubedb
- The user has read/write access to above mentioned database
- Create
sonarqube-postgres
service insonarqube
namespace that points to the psql database - Create
sonarqube-postgres
secret insonarqube
namespace with the keypassword
that contains the password to the user for the psql database