- Shell 92.8%
- Python 2.9%
- HTML 2.3%
- Dockerfile 1.1%
- Go Template 0.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Christoph Görn
f14ae3e24a
Phase 2b of the hostname cutover. Flips DOMAIN and ROOT_URL, so the UI,
cookies, OIDC callback and every clone URL Forgejo advertises now name
git.b4mad.industries.
forgejo.b4mad.net stays in the ingress indefinitely rather than
redirecting-and-retiring. Existing clone remotes, registry image refs
and API callers all still name it, and none of those follow an HTTP
redirect — git and container clients treat the old host as identity,
not as a location.
SSH clone URLs move too, implicitly: no SSH_DOMAIN is set, so it
derives from DOMAIN. The new host was verified answering on :2222
before this commit — the NodePort is port-based, so both names reach
the same listener with the same host key.
Safe because
|
||
| .beads | ||
| .claude | ||
| .github/ISSUE_TEMPLATE | ||
| .tekton | ||
| docs | ||
| images | ||
| manifests | ||
| scripts | ||
| secrets | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .gitleaks.toml | ||
| .gitleaksignore | ||
| .mcp.json | ||
| .pre-commit-config.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| FUNDING.json | ||
| LICENSE | ||
| OWNERS | ||
| README.md | ||
| releaserc.toml | ||
op1st DevSecOps by #B4mad
This repository implements Operate First SIG/SRE Infrastructure Services
and partialy Hybride Cloud Patterns: Multicluster DevSecOps
It is also available via radicle as rad:z2y94Zx8RUfQBNQD2nSpPLN5CW7NQ.
Service Status
Operate First Infrastructure Services
On the nostromo environment we have deployed and configured the following infrastructure services:
- Operate First GitOps
- Operate First Pipelines
- Open Policy Agent Gatekeeper
These services are deployed on the nostromo environment.
Hosted community services
We follow an app-of-apps pattern, where we have a single kustomization.yaml file that references all other manifests,
it can be found in the manifests/applications/app-of-apps.yaml file.
Directory Structure
All kustomize manifests are located below the manifests/ directory.
Component manifests
Manifests that are generally useful or applicable are located in the component/ directory. These are not intended
to be deployed directly, but rather used as a reusable component for other (environment specific) manifests.
Organizational Unit scoped manifests
These manifests are valid and applicaple to the whole #B4mad organizational unit of Operate First, they should be deployed to each of our clusters.
Cluster scoped manifests
These manifests are valid and applicable to a single cluster, they should be deployed to a cluster. They are agnostic to any organizational unit and implement a specific functionality/configuration that is generally applicable.
Environment scoped manifests
These manifests are valid and applicable to a single environment, they should be deployed to a cluster and may reference ou or cluster scoped manifests. They implement a specific functionality/configuration that is specific to a single environment.
A few of the configurations recommended for Single-Node OpenShift have been implemented as well.
Usage
To configure a specific environment, run kustomize build manifests/environments/nostromo | oc apply -f -
Funding
If you like this project, or depend on it, feel free to support it via the drips.network and check out https://www.drips.network/app/projects/github/b4mad/op1st-emea-b4mad