Crossplane Providers Expand the Control Plane's Credential Surface
Crossplane turns Kubernetes into a control plane for external infrastructure. Providers install APIs and controllers that manage outside resources. The convenience comes with a larger credential and authorization surface than a plain application deployment.
An internet search for the Crossplane name may identify candidate pages. It cannot show which provider packages are installed, which cloud identities they use, or which subjects can create managed resources.
Providers run inside the cluster
Crossplane's provider documentation says providers may create Deployments, Service Accounts, and RBAC configuration. A provider runtime can use a ProviderConfig that points to credentials stored in a Kubernetes Secret, the pod filesystem, or an environment variable.
Each choice changes the credential boundary. A Secret is still cluster data that must be protected. A mounted file must be controlled by the pod and image.…