A FIPS-compliant notification controller for Flux CD, designed for enterprise Kubernetes environments. This container provides secure event handling and notification delivery for GitOps workflows, with added compatibility for Bitnami environments and FIPS 140-2 validation.
Core capabilities and strengths of this container
Typical scenarios where this container excels
Download the container image from the registry
docker pull clnstrt-images.cleanstart.com/$ORGANIZATION/flux-notification-controller-bitnami-compat-fips:latestdocker pull clnstrt-images.cleanstart.com/$ORGANIZATION/flux-notification-controller-bitnami-compat-fips:latest-devRun the container with basic configuration
docker run -it --name flux-notification-controller clnstrt-images.cleanstart.com/$ORGANIZATION/flux-notification-controller-bitnami-compat-fips:latestDeploy with production security settings
docker run -d --name flux-notification-controller \
--read-only \
--security-opt=no-new-privileges \
--user 1000:1000 \
-v /etc/flux/notifications:/etc/flux/notifications \
clnstrt-images.cleanstart.com/$ORGANIZATION/flux-notification-controller-bitnami-compat-fips:latestMount local directory for persistent data
docker run -v $(pwd)/notifications:/etc/flux/notifications clnstrt-images.cleanstart.com/$ORGANIZATION/flux-notification-controller-bitnami-compat-fips:latestRun with custom port mappings
docker run -p 9292:9292 clnstrt-images.cleanstart.com/$ORGANIZATION/flux-notification-controller-bitnami-compat-fips:latestConfiguration options available through environment variables
info:9292true2Recommended security configurations and practices
Recommended security context for Kubernetes deployments
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
seccompProfile:
type: RuntimeDefaultEssential links and resources for further information