Christopher Haar

@turkenh remember we set storage version v1beta1 lot of releases ago - what happen with users still using v1alpha1 before this time and want to switch to v1beta1 ?

https://github.com/haarchri/issue-helm-213 create release first with v1alpha1 https://github.com/haarchri/issue-helm-213/blob/main/apis/composition.yaml#L22 then change to v1beta1 and add a field which is only available in v1beta1 https://github.com/haarchri/issue-helm-213/blob/main/apis/composition-update.yaml#L22 and https://github.com/haarchri/issue-helm-213/blob/main/apis/composition-update.yaml#L31 reproduce the issue: ``` ./setup.sh wait...

this is supported - and working Can you share your Setup of the IRSA Role ? If you using vpc endpoints make Sure your crossplane can can reach the vpc...

crossplane will fetch the package via IRSA and then Setup CRDs + Deployment - what is configured for the deployment depends on DeploymentRuntimeConfig

we using IRSA to pull packages from private ECR with simple annotate the serviceAccount with an role + policy Can you share your issue ? kubectl get pkgrev ?

We have one missleading logging/ discard logging around which reminds me of: https://github.com/crossplane/crossplane/issues/5805

this is exactly handled by this code path: > this is supported - and working > Can you share your Setup of the IRSA Role ? If you using vpc...

i shared with @jwitko an image to remove the `io.discard` that we can see some more insights are the Node Roles with an ECR Policy? Because they need to pull...

this will work with **IRSA** and **PodIdentity** - you need a IAM Role for your crossplane service account - something like: ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow",...

here a full run with PodIdentity: Create a Kind Cluster: ``` kind create cluster --name chris-cluster ``` Install Crossplane: ``` helm install crossplane \ --namespace crossplane-system \ --create-namespace crossplane-stable/crossplane ```...