---
schema_version: "1"
id: 3210c799929d3fc987cafb1652b15cb807f31a794eec3e226330201a0e5713e7
title: Mule App Deployments Kubernetes Permissions on Runtime Fabric
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/latest/rtf-mule-app-permissions.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/latest/rtf-mule-app-permissions
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5a418df8968bc29c4c3f2980f9ec0064c42a46cebfbb0bc0f0d0582c6c7d6548
description: MuleSoft Documentation Site
release: "3.0"
latest: true
---
---
product: Runtime Fabric
version: 3.0
is-latest-version: true
---

# Mule App Deployments Kubernetes Permissions on Runtime Fabric

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Mule apps deployed on the Runtime Fabric platform do not access the underlying Kubernetes API
server. By default, Mule app deployments do not have RBAC configurations (`Role` and
`Rolebindings`).

However, if the Mule app use case requires K8s (Kubernetes) API access, you can override this
behavior by enabling the `automountserviceaccounttoken` via customization CRD (custom resource
definition) and attach a `Role` (customer-owned) with a `Rolebinding` (customer-owned) to the
service account that Runtime Fabric core software creates per deployment. Refer to
[Customizing Mule App Kubernetes Resources](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd).

## See Also

- [Runtime Fabric Control Plane Permissions](https://docs.mulesoft.com/runtime-fabric/latest/rtf-permissions)

- [Enabling RTFCTL Kubernetes Permissions](https://docs.mulesoft.com/runtime-fabric/latest/rtfctl-permissions)

- [Configuring Kubernetes for Runtime Fabric](#)