crossplane-provider-family-gcp-beta

packaged by Chainguard

Chainguard Container for crossplane-provider-family-gcp-beta

Crossplane upjet family provider for Google Cloud Platform Beta APIs (config/ProviderConfig).

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/crossplane-provider-family-gcp-beta: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 Crossplane GCP Beta providers are comparable to upstream Upbound GCP Beta providers with the following architectural differences:

• Upstream providers can be deployed independently and automatically resolve their dependencies
• Chainguard providers require manual installation of the family provider and use skipDependencyResolution: true for component providers to prevent automatic upstream dependency resolution
• Deployment pattern: Install the Chainguard family provider first, then add individual component providers as needed

The Chainguard crossplane-provider-family-gcp-beta container image is a drop-in replacement for the upstream xpkg.upbound.io/upbound/provider-family-gcp-beta image.

Getting Started

Install Crossplane

helm repo add crossplane-stable https://charts.crossplane.io/stable
helm repo update
helm install crossplane --namespace crossplane-system --create-namespace crossplane-stable/crossplane

Install the Family Provider

The family provider supplies the shared ProviderConfig CRD used by every GCP Beta service-scoped sub-provider (e.g. crossplane-provider-gcp-beta-compute, -container, -cloudplatform, -networksecurity). It must be installed before any GCP Beta component providers:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-family-gcp-beta
spec:
  package: cgr.dev/ORGANIZATION/crossplane-provider-family-gcp-beta:latest

Then add each GCP Beta component provider you need with skipDependencyResolution: true, for example the compute-beta provider:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-gcp-beta-compute
spec:
  package: cgr.dev/ORGANIZATION/crossplane-provider-gcp-beta-compute:latest
  skipDependencyResolution: true

Apply the manifests and verify the providers are healthy:

kubectl apply -f provider.yaml
kubectl get providers

Configuration

After installing providers, configure GCP credentials using a ProviderConfig from the shared family CRD. Create a Kubernetes Secret holding a GCP service account key JSON, then reference it from a ProviderConfig:

# Create credentials secret from a GCP service account key file
kubectl create secret generic gcp-secret \
  --namespace crossplane-system \
  --from-file=creds=./gcp-credentials.json

# Create ProviderConfig
cat <<EOF | kubectl apply -f -
apiVersion: gcp.upbound.io/v1beta1
kind: ProviderConfig
metadata:
  name: default
spec:
  projectID: my-gcp-project
  credentials:
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: gcp-secret
      key: creds
EOF

Upstream Equivalent

Documentation and Resources

• Upbound GCP Beta Provider Documentation
• Crossplane Getting Started Guide
• GCP Beta Provider Examples

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.