Pre-built Zarf Package of a Software Factory (a.k.a. "DI2-ME")
🚧 This project is still early in its development. Early adopters are expected to have a good understanding of how Kubernetes works as well as how to operate and maintain the various services present in this package. This package is intended to significantly speed up the initial deployment and configuration of a software factory, as well as provide a simple upgrade path for updates and security fixes. It will not absolve the user from understanding what it takes to operate a software factory in a production setting. We plan to transition to an open beta soon™ (maybe sooner if any smarties out there want to come help out 😄), where we will anticipate people starting to use this package operationally, with the caveat that it will require a lot more care and feeding than we intend it to require by the time version 1.0 releases.
Deploys the components of a software factory with the following services, all running on top of Big Bang Core:
- GitLab*
- GitLab Runner*
- Minio Operator*
- Nexus*
- Jira
- Confluence
- Jenkins
Coming Soon:
- SonarQube*
- Mattermost*
*Deployed using Big Bang Umbrella
All versions of this package will not be compatible with all versions of Zarf. Here's a compatibility matrix to use to determine which versions match up
| Package Version | Zarf Version |
|---|---|
| 0.0.2 - main | v0.15.0+ |
| 0.0.1 | v0.14.0 |
-
Jenkins won't work in disconnected environments due to its dependency on plugins pulled from the internet. Work is needed to figure out and implement a method of doing locally sourced plugins.
-
Due to issues with Elasticsearch this package doesn't work yet in some k8s distros. It does work in K3s (using
zarf init --components k3s,gitops-service). Upcoming work to swap the EFK stack out for the PLG stack (Promtail, Loki, Grafana) should resolve this issue. Keep in mind the big note above about the package being huge. Unless you have the Mother of All Laptops you'll need to turn a bunch of stuff off before you try to deploy it locally using Vagrant. -
If you are using Vagrant, inside the Vagrant VM the services are available on the standard port 443. Outside the VM if you want to pull something up in your browser that traffic is being routed to port 8443 to avoid needing to be root when running the Vagrant box.
- Logged into registry1.dso.mil
makepresent in PATHsha256sumpresent in PATH- TONS of CPU and RAM. Our testing shows the AWS EC2 instance type m6i.8xlarge works pretty well at about $1.50/hour, which can be reduced further if you do a spot instance.
- Vagrant and VirtualBox, only if you are going to use a Vagrant VM, which is incompatible when using an EC2 instance.
Note that having Zarf installed is not a prerequisite. This repo pulls in its own version of Zarf so that it can be versioned separately from whatever your system has installed. To change the version of Zarf used modify the ZARF_VERSION variable in the Makefile