dhi.io/oathkeeper-maester
Ory Oathkeeper Maester
Kubernetes controller that watches Ory Oathkeeper Rule custom resources and renders them into the access rules ConfigMap or file that Ory Oathkeeper consumes.
pushed 2 days ago
linux/amd64, linux/arm64
42.12 MB
for linux/amd64
154
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Ory Oathkeeper Maester
Ory Oathkeeper Maester is a Kubernetes controller for Ory Oathkeeper access rules. It watches Rule custom resources in
the oathkeeper.ory.sh/v1alpha1 API group, validates the handlers they reference, and renders every valid rule into the
JSON access rules document that Oathkeeper reads, so access rules are managed as Kubernetes objects instead of a
hand-edited file.
It runs in one of two modes: as a standalone controller Deployment that writes the rules into a ConfigMap mounted by Oathkeeper, or as a sidecar container next to Oathkeeper that writes the rules to a shared file. Maester is developed by the Ory community and is not actively maintained by the Ory core maintainers.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Ory and Ory Oathkeeper are trademarks of Ory Corp. Kubernetes® is a registered trademark of The Linux Foundation. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.