docs(guides): add crossplane with workload-identity guide #1047
+787
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

This PR adds docs for configuring Crossplane to pull packages from private cloud provider container registries using Kubernetes Workload Identity.
Users frequently encounter issues when trying to use Crossplane with private container registries in managed Kubernetes environments like EKS, AKS, and GKE. While Crossplane already supports workload identity authentication, the setup process and prerequisites are not well documented. This leads to confusion and issue requests, as seen in crossplane/crossplane#6137.
The guide provides step-by-step instructions for configuring workload identity with Crossplane across AWS EKS with IAM Roles for Service Accounts and ECR, Azure AKS with Azure Workload Identity and ACR, and Google Cloud GKE with GKE Workload Identity and Artifact Registry.
This guide helps users leverage Crossplane's existing workload identity support without requiring static credentials or imagePullSecrets.