Feature Request: Support for Configuring Permissions for Cloud Run via Crossplane to Resolve 'Error: Forbidden

[noorulqumar]

When creating Cloud Run services using Crossplane, I encountered the error: "Error: Forbidden - Your client does not have permission to get URL / from this server."

While I can resolve this issue manually via the GCP console by adjusting permissions,

After this, I'm able to access it successfully.

I would like to request a feature to handle these permissions directly through Crossplane configurations. This would streamline the process of managing Cloud Run services without requiring additional steps in the GCP console. Having this capability in Crossplane would significantly improve the user experience by ensuring all necessary permissions are handled declaratively.

This is the config I have right now to create a Cloud Run service.

apiVersion: cloudrun.gcp.upbound.io/v1beta1
kind: Service
metadata:
  annotations:
    meta.upbound.io/example-id: cloudrun/v1beta1/service
  labels:
    testing.upbound.io/example-name: cloudrun-service
  name: cloudrun-service
spec:
  providerConfigRef:
    name: providerconfig
  forProvider:
    location: us-central1
    template:
      - spec:
          - containers:
              - image: us-docker.pkg.dev/cloudrun/container/hello
              
    traffic:
      - latestRevision: true
        percent: 100

This is the Provider detail

https://marketplace.upbound.io/providers/upbound/provider-gcp-secretmanager/v1.8.3/resources/secretmanager.gcp.upbound.io/Secret/v1beta1#doc:spec-forProvider-annotations

[mattkirby]

Google documentation describes how to do this here https://cloud.google.com/run/docs/authenticating/public

The documentation tells you that you can create an IAM binding for permitting unauthenticated access by setting the role "roles/run.invoker" for the user "allUsers". See https://marketplace.upbound.io/providers/upbound/provider-gcp-cloudrun/v1.9.0/resources/cloudrun.gcp.upbound.io/ServiceIAMMember/v1beta1 for the ServiceIAMMember documentation. I have validated that this allows unauthenticated access to a Cloud Run deployment.

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.