dhi.io/azure-service-operator
Azure Service Operator
Azure Service Operator allows you to create Azure resources using kubectl.
pushed 19 hours ago
linux/amd64, linux/arm64
167.09 MB
for linux/amd64
180
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 Azure Service Operator
Azure Service Operator (ASO) is a Kubernetes operator that enables you to provision and manage Azure resources directly
from within your Kubernetes cluster using native Kubernetes tooling. Instead of managing Azure resources through the
Azure portal or CLI, ASO allows you to define Azure resources as Kubernetes Custom Resources and manage them using
familiar tools like kubectl apply.
ASO consists of:
- Custom Resource Definitions (CRDs) for each Azure service that can be provisioned
- Kubernetes controller that synchronizes the desired state defined in Custom Resources with the actual state of resources in Azure
- Code-generated resources based on Azure OpenAPI specifications, enabling rapid support for new Azure services
Key features of Azure Service Operator:
- Declarative Azure resource management: Define Azure infrastructure as Kubernetes manifests using
kubectl apply - GitOps compatibility: Manage Azure resources through your existing GitOps workflows and CI/CD pipelines
- Code-generated CRDs: Automatically generated from Azure REST API specifications, ensuring comprehensive coverage of Azure services
- Rich status information: View the actual state of Azure resources through Kubernetes, including server-side applied defaults
- Authentication flexibility: Support for Service Principal, Managed Identity, and Workload Identity authentication methods
- Multi-tenant support: Operate across multiple Azure tenants and subscriptions from a single operator instance
- Namespace isolation: Control which namespaces the operator monitors for Azure resource definitions
ASO v2 (the current stable version) provides significant improvements over v1:
- More uniform resource definitions due to code generation
- Faster support for new Azure API versions
- Clearer resource states through Ready conditions
- Dedicated storage versions for better upgrade experiences
Common use cases include:
- Provisioning Azure databases, storage accounts, and virtual networks from Kubernetes
- Managing Azure resources as part of application deployment manifests
- Implementing infrastructure-as-code practices using Kubernetes-native workflows
- Integrating Azure resource lifecycle with Kubernetes application lifecycle
This Docker Hardened Image packages the Azure Service Operator v2 controller in a secure, minimal container optimized for production Kubernetes environments.
For more information about Azure Service Operator, visit the official documentation at https://azure.github.io/azure-service-operator/.
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 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
Microsoft® and Azure® are registered trademarks of Microsoft Corporation. All rights in the marks are reserved to Microsoft Corporation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.