Christopher Haar
Christopher Haar
is this still relevant ? so we can simply add the following manifest like classic provider-aws ``` --- apiVersion: aws.jet.crossplane.io/v1alpha1 kind: ProviderConfig metadata: name: example spec: credentials: source: None ```
Can you open a PR here ? Then we can bring it in
is this error still valid ? i can see in our environment everything is working as expected ``` Status: At Provider: Arn: arn:aws:iam::xxxx:instance-profile/karpenter Create Date: 2022-08-26T10:20:16Z Instance Profile ID: AIPAV32PT5M2E5JSY77CU...
Can you remove complete Routes in RouteTable and use only Route resource ? Does this make a difference ?
@muvaf any chance to check this change ? or is this something for the runtime ?
Thanks - can you Check for DCO ?
@airwalk225 can you update your DCO signing ? thanks
tested the enhancement - thanks @AlessandroBenoni can you rebase ?
@AlessandroBenoni thanks for driving this PR we will going on with https://github.com/crossplane-contrib/provider-aws/pull/1644
think you can see the error in events on the resource level ?