Examples
Examples
Concrete manifests and expected reconciliation outcomes for common InferenceIdentityBinding flows.
Reusable reference inputs for e2e tests and demo docs live under
test/reference/inference-environment/. Those manifests represent externally
managed workload and GAIE resources that exist before kleym-operator
reconciles a binding.
Before You Apply Examples
These examples assume:
- Gateway API Inference Extension (GAIE) CRDs are installed for
InferencePool - SPIFFE Runtime Environment (SPIRE) Controller Manager is installed with the
ClusterSPIFFEIDCRD kleym-operatoris running- the required identity-boundary admission policy controls the fixed variant label and makes it immutable for each Pod lifetime
The manifests show the GAIE fields kleym-operator consumes. For full GAIE
object shape and additional optional fields, use the GAIE API types index.
For SPIFFE and SPIRE background, see SPIFFE overview and SPIRE concepts.
Example Paths
| Example | Use it when | Outcome |
|---|---|---|
| Basic Binding | You need one identity for a service account and label-defined pool variant. | One managed ClusterSPIFFEID for the declared variant. |
Recommended Reading Order
- Start with Basic Binding to validate end-to-end wiring.
- Review Conditions and Troubleshooting if reconciliation does not reach
Ready=True.
Last updated on