Chainguard Container for onepassword-operator

The 1Password Connect Kubernetes Operator provides the ability to integrate Kubernetes Secrets with 1Password

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/onepassword-operator:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's onepassword-operator container is a lean, Wolfi-based container image. It is functionally equivalent to the 1password/onepassword-operator while maintaining minimal dependencies and enhanced security.

Getting Started

Prerequisites

Before installing the operator, you'll need:

1. A 1Password account with Secrets Automation permissions
2. The 1password-credentials.json file from your Connect server setup
3. A Connect token

NOTE: See the Connect Server guide to set up a server and get your credentials file and token.

Installation with Helm

Install the operator with Chainguard images:

helm repo add 1password https://1password.github.io/onepassword-operator/
helm repo update

helm install onepassword \
  1password/connect \
  --namespace onepassword \
  --set-file connect.credentials=1password-credentials.json \
  --set operator.create=true \
  --set operator.imageRepository=cgr.dev/ORGANIZATION/onepassword-operator \
  --set operator.version=latest \
  --set operator.token.name=$(op connect token create <token_name> --server <server_id_or_name> --vaults <vault_id_or_name>)

Create a OnePasswordItem

Once the operator is running, you can create OnePasswordItem resources to sync 1Password items to Kubernetes Secrets:

apiVersion: onepassword.com/v1
kind: OnePasswordItem
metadata:
  name: my-secret
spec:
  itemPath: "vaults/<vault_id_or_title>/items/<item_id_or_title>"

NOTE: you must replace <vault_id_or_title> and <item_id_or_title> with your actual vault and item identifiers.

The operator will automatically create a Kubernetes Secret with the same name containing all fields from the 1Password item.

You can check the secrets created to make sure that everything is working correctly:

kubectl get secrets

and check the contents of the secret:

kubectl get secret <name_of_your_item> -o yaml

Documentation and Resources

For comprehensive documentation and additional configuration options, please refer to:

• 1Password Operator Documentation - Official documentation for the 1Password Kubernetes Operator
• 1Password Connect Server Documentation - Setup and configuration guide for Connect Server
• 1Password Operator GitHub Repository - Source code and issue tracking

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.