Closed edgarsilva948 closed 4 months ago
Can you show kubectl get pkgrev ?
the family provider needs to be installed from the same registry then the providers - otherwise the RBAC Manager will not add the permissions
and it looks like you have multiple times spec.package wich override your first
Can you please clarify why it is necessary to have the same registry for all the image providers? Is this a bug or an expected behavior?
$ kubectl get pkgrev
providerrevision.pkg.crossplane.io/provider-upjet-aws-apigateway-522f26dcf869 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-apigateway:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-cloudfront-6ade770a3698 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-cloudfront:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-cloudwatch-a574cf0b7903 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-cloudwatch:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-cloudwatchlogs-4f0b0596620a True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-cloudwatchlogs:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-dynamodb-30524fc5a5bd True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-dynamodb:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-ec2-9992fffc7b00 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-ec2:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-eks-287ac2697d84 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-eks:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-elasticache-021e92bd0c1b True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-elasticache:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-elbv2-99de9eeb558d True 1 222222222222.dkr.ecr.REGION.amazonaws.com/upbound/provider-aws-elbv2:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-fc9896a8d96a True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-family-aws:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-iam-b29203ad115c True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-iam:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-kms-8713a070abe3 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-kms:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-lambda-7f8fe1d557bf True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-lambda:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-mq-9e573a8c1f29 True 1 222222222222.dkr.ecr.REGION.amazonaws.com/upbound/provider-aws-mq:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-rds-7a0b2a843a4b True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-rds:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-s3-6cbd0623c595 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-s3:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-sns-51f29cdcc163 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-sns:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-sqs-04017876a5e0 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-sqs:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-vpc-b43bc957fed5 True 1 111111111111.dkr.ecr.REGION.amazonaws.com/REPO-PATH/upbound/provider-aws-vpc:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-waf-797914a35bea True 1 222222222222.dkr.ecr.REGION.amazonaws.com/upbound/provider-aws-waf:v1.6.0 Active 6d20h
providerrevision.pkg.crossplane.io/provider-upjet-aws-wafregional-7bf10629d9c1 True 1 222222222222.dkr.ecr.REGION.amazonaws.com/upbound/provider-aws-wafregional:v1.6.0 Active 6d20h
yes the RBAC Manager expecting that the Providers from the Same org / registry to grant permissions
is there any documentation or references that explain this behavior of the RBAC Manager expecting providers to be from the same organization/registry to grant permissions? It would be helpful to understand this requirement in more detail.
Is there an existing issue for this?
Affected Resource(s)
elbv2.aws.upbound.io/v1beta1 - LB elbv2.aws.upbound.io/v1beta1 - LBTargetGroup elbv2.aws.upbound.io/v1beta1 - LBTargetGroupAttachment elbv2.aws.upbound.io/v1beta1 - LBListener
Resource MRs required to reproduce the bug
Steps to Reproduce
DeploymentRuntimeConfig
with the provided configuration.Provider
with the provided configuration.Provider
with the provided configuration.ProviderConfig
with the provided configuration.What happened?
Actual Behavior
The
elbv2
provider deployment succeeds, but attempts to create any resource using the provider result in failure, accompanied by permission errors in the logs. The service account used by the provider does not have sufficient permissions to listProviderConfig
resources, preventing resource creation.Expected Behavior
The AWS provider's service account should have sufficient permissions to list
ProviderConfig
resources in theaws.upbound.io
API group. This would allow the provider to create resources without encountering errors.Relevant Error Output Snippet
Crossplane Version
v1.16.0
Provider Version
v1.6.0
Kubernetes Version
Client Version: v1.30.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.6-eks-db838b0
Kubernetes Distribution
EKS
Additional Info
If I manually add
cluster-admin
permission to the service account, the providers work perfectly.