How to Configure Zapier Kubernetes Read Only Access

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up zapier kubernetes read only access by linking a Zapier webhook to a Kubernetes role. This role must allow only read verbs on specific cluster resources. Many teams start by giving automation tools broad cluster admin keys to save time. That choice lets a single bad workflow change pods, delete workloads, or read private secrets. How to set up zapier kubernetes read only access First, you create a dedicated account in Kubernetes just for your Zapier workflows. Next, you build a Role

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up zapier kubernetes read only access by linking a Zapier webhook to a Kubernetes role. This role must allow only read verbs on specific cluster resources. Many teams start by giving automation tools broad cluster admin keys to save time. That choice lets a single bad workflow change pods, delete workloads, or read private secrets.

How to set up zapier kubernetes read only access

First, you create a dedicated account in Kubernetes just for your Zapier workflows. Next, you build a Role or a ClusterRole with strict read rules. In Kubernetes RBAC, a Role sets permissions inside one single namespace. A ClusterRole covers the whole cluster, including nodes or resources across all namespaces. Most teams should pick a Role to keep the automation inside one namespace.

In Kubernetes RBAC, permissions are additive, and there are no deny rules. You must list only the exact resources and read verbs that Zapier needs. You also need to watch out for subresources in the API URL. Kubernetes RBAC writes a subresource with a slash, like a pod log endpoint. If Zapier must read pod logs, your rule must include that exact subresource. Once the Role is ready, you link it to the account with a RoleBinding. A RoleBinding grants those read rules inside that one specific namespace. If you use a ClusterRoleBinding instead, it grants those rules across the whole cluster.

Finally, you set up your Zapier action to call the Kubernetes API endpoint. The workflow sends its request with the token tied to your new read role. Kubernetes checks the RBAC API group to see if the request matches your rules. If the workflow tries to create or delete a pod, the API blocks it.

What native RBAC solves and what it leaves open

Native Kubernetes RBAC is great at stopping write actions from automation tools. It ensures that a Zapier workflow can only read the resources you listed. It also keeps your automation from deleting workloads or changing cluster state. By using a RoleBinding in one namespace, you limit what the workflow can reach.

Auditor Read-Only Access + Kubernetes API Server Access: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Still, native RBAC only checks who can log in and which endpoints they call. It does not inspect the actual data inside the response during the request. For example, a read rule on pod logs returns every line of text. Those logs often hold user emails, phone numbers, card numbers, or national IDs. Once Kubernetes approves the read request, all that raw data flows out to Zapier. Native RBAC also relies on static keys or tokens stored inside the external tool. If someone copies that token from Zapier, they can run read calls from anywhere. Native roles decide who gets in, not what happens to sensitive data in flight.

Why static automation keys create audit blind spots

When multiple Zapier workflows share one Kubernetes account, your cluster logs lose detail. Every API call shows up under the same generic role name in the logs. Your team cannot tell which specific workflow or user triggered a given read call. Rotating that shared key is also hard because updating it can break active workflows. Teams need a way to check requests in flight and mask sensitive fields by default. Rewriting matched fields like emails or card numbers in results keeps sensitive data safe.

Govern kubectl and API calls in flight

Identity providers and Kubernetes RBAC decide who logs into a cluster. They cannot redact keys inside returned JSON objects or hold a risky delete call for review. By design, hoop.dev runs as an open-source proxy, a sidecar for your Kubernetes API, checking requests and responses without replacing RBAC.

First, hoop.dev guardrails refuse banned methods, paths, or headers before they run. Next, hoop.dev data masking rewrites sensitive keys in returned Secret, ConfigMap, and log responses in memory, and writes each decision to the audit trail. Explore the repo on GitHub.

Frequently asked questions

Should I use a Role or a ClusterRole for Zapier workflows?

Use a Role and a RoleBinding whenever your workflow only checks one namespace. Use a ClusterRole only when Zapier must read cluster-wide objects like nodes.

Can I add a deny rule to block Kubernetes secrets in RBAC?

No, Kubernetes RBAC permissions are purely additive and have no deny rules. You must leave secrets out of your allowed resource list from the start.

How do I let Zapier read pod logs without giving pod write rights?

Grant read verbs on the pods log subresource in your Kubernetes Role. This lets the workflow fetch log text without allowing pod changes or command execution.

The query runs. The emails stay hidden.