v0.42.1

This release backports the PR addressing the regression related to IAM roles and role policy attachments introduced in version 0.40.0

After upgrading from the affected version to this version, make sure to unset the spec.forProvider.managedPolicyArns value from any Role.iam.aws.upbound.io managed resources that you want to be able to use RolePolicyAttachment resources to attach policies to. You will need to run a script like the following as suggested by @mbbush in this comment.

kubectl get role.iam.aws.upbound.io -o name | xargs kubectl patch --dry-run=server --patch '[{"op":"remove","path":"/spec/forProvider/managedPolicyArns"}]' --type=json

What's Changed

• [release-0.42] Backport #933 by @turkenf in #993

Full Changelog: v0.42.0...v0.42.1

v0.41.1

This release backports the PR addressing the regression related to IAM roles and role policy attachments introduced in version 0.40.0

After upgrading from the affected version to this version, make sure to unset the spec.forProvider.managedPolicyArns value from any Role.iam.aws.upbound.io managed resources that you want to be able to use RolePolicyAttachment resources to attach policies to. You will need to run a script like the following as suggested by @mbbush in this comment.

kubectl get role.iam.aws.upbound.io -o name | xargs kubectl patch --dry-run=server --patch '[{"op":"remove","path":"/spec/forProvider/managedPolicyArns"}]' --type=json

What's Changed

• [release-0.41] Backport #933 by @turkenf in #992

Full Changelog: v0.41.0...v0.41.1

v0.40.1

This release backports the PR addressing the regression related to IAM roles and role policy attachments introduced in version 0.40.0

After upgrading from the affected version to this version, make sure to unset the spec.forProvider.managedPolicyArns value from any Role.iam.aws.upbound.io managed resources that you want to be able to use RolePolicyAttachment resources to attach policies to. You will need to run a script like the following as suggested by @mbbush in this comment.

kubectl get role.iam.aws.upbound.io -o name | xargs kubectl patch --dry-run=server --patch '[{"op":"remove","path":"/spec/forProvider/managedPolicyArns"}]' --type=json

What's Changed

• [release-0.40] Backport #933 by @turkenf in #991

Full Changelog: v0.40.0...v0.40.1

v0.44.0

In v0.44.0, the Upjet version has been upgraded to v1.0.0. This upgrade, brings a change with how we interact with the underlying Terraform AWS provider. Instead of interfacing with TF CLI, the new implementation consumes the Terraform provider's Go provider schema and invokes the CRUD functions registered in that schema. All resources except the following 5 resources will be reconciled using the new architecture:

* `SecurityGroupIngressRule.ec2`
* `SecurityGroupEgressRule.ec2`
* `Environment.appconfig`
* `UserPoolClient.cognitoidp`
* `Domain.simpledb`

In this version, many performance improvements have been made with the introduction of the new architecture. Below is a reference results for 1K and 10K MR. These results are shared not to provide a Sizing Guide but as a reference to understand the improvements in performance metrics. Also, the experiment sets of tests are shared:

• Objective: 10K UserPolicyAttachment MRs

• Parallelization: 500 reconcile workers

• Poll period: 10min

• Node: m5.2xlarge (8vCPU, 32GiB RAM)

  Average TTR	Peak TTR	Average Memory	Peak Memory	Average CPU	Peak CPU
  4.40 secs	79 secs	775.41 MiB	1185.62 MiB	15.25%	20.90%

• Objective: 1K UserPolicyAttachment MRs

• Parallelization: 500 reconcile workers

• Poll period: 10min

• Node: m5.2xlarge (8vCPU, 32GiB RAM)

  Average TTR	Peak TTR	Average Memory	Peak Memory	Average CPU	Peak CPU
  4.15 secs	44 secs	630.39 MiB	948.35 MiB	9.06%	12.69%

Note

While there are no breaking changes in the APIs of the CRDs, we encourage users who may have made changes to the ControllerConfig to adjust previous values like max-reconcile-rate to undo these and work with the default settings of the provider. We will release a sizing and configuration guide in the near future to give guidance on how users might consider adjusting the default behavior.

What's Changed

• Fix MetricFilter.cloudwatchlogs external-name configuration by @ulucinar in #943
• Bump crossplane-runtime to v1.14.1 by @turkenf in #947
• add bucket id,arn and regio to writeConnectionSecretToRef by @ahmedali6 in #951
• Fix broken link for adding new resource by @turkenf in #962
• Update kubernetes patches to v0.28.4 by @renovate in #967
• Use Terraform Plugin SDK to Reconcile MRs by @ulucinar in #938

New Contributors

• @ahmedali6 made their first contribution in #951

Full Changelog: v0.43.1...v0.44.0

v0.43.1

This release updates Crossplane Runtime to v1.14.1 which includes a fix in the retry mechanism while persisting the critical annotations.

What's Changed

• [Backport release-0.43] Bump crossplane-runtime to v1.14.1 by @github-actions in #948

Full Changelog: v0.43.0...v0.43.1

v0.43.0

What's Changed

• Msk serverless cluster by @nalbury in #905
• Add "branch_name", "version" and "regorg" parameters to the "Publish Service Artifacts" workflow by @ulucinar in #925
• Update actions/checkout digest to b4ffde6 by @renovate in #926
• fix(iam-role): ignore managed_policy_arns in late init by @haarchri in #933
• Update kubernetes patches by @renovate in #659

New Contributors

• @nalbury made their first contribution in #905

Full Changelog: v0.42.0...v0.43.0

v0.42.0

What's Changed

Important

Provider version 0.40 introduced a regression (see #929) related to IAM roles and role policy attachments. The issue was fixed in provider version 0.43.0. If you haven't installed versions 0.40.0, 0.41.0 or 0.42.0 into your cluster, we recommend skipping those releases and upgrading directly to 0.43.0 when you choose to upgrade. If you have installed one of the affected releases, we recommend upgrading to an unaffected release (0.43+), and then you will need to unset the spec.forProvider.managedPolicyArns value from any Role.iam.aws.upbound.io managed resources that you want to be able to use RolePolicyAttachment resources to attach policies to.

• Resolve name collision between S3 and Lightsail in quickstart by @mergenci in #811
• Update alpine Docker tag to v3.18.4 by @renovate in #900
• Uptest family providers by @ulucinar in #903
• Fix trailing apostrophe breaking a hyperlink by @jastang in #897
• Bump uptest to v0.6.0 by @ulucinar in #913
• Bump uptest to v0.6.1 by @ulucinar in #914
• feat(ec2): add aws_vpc_security_group_ingress/egress_rule resource by @huynhsontung in #685
• Bump build submodule to 2672eeb by @jastang in #916
• Replace Go module dependency github.com/upbound/upjet with github.com/crossplane/upjet by @ulucinar in #919
• Sync UP_VERSION in Makefile by @jastang in #921
• Bump crossplane-runtime, upjet dependency to master and GMP promote to BETA by @turkenf in #918

New Contributors

• @mergenci made their first contribution in #811
• @huynhsontung made their first contribution in #685

Full Changelog: v0.41.0...v0.42.0

v0.41.0

What's Changed

Important

Provider version 0.40 introduced a regression (see #929) related to IAM roles and role policy attachments. The issue was fixed in provider version 0.43.0. If you haven't installed versions 0.40.0, 0.41.0 or 0.42.0 into your cluster, we recommend skipping those releases and upgrading directly to 0.43.0 when you choose to upgrade. If you have installed one of the affected releases, we recommend upgrading to an unaffected release (0.43+), and then you will need to unset the spec.forProvider.managedPolicyArns value from any Role.iam.aws.upbound.io managed resources that you want to be able to use RolePolicyAttachment resources to attach policies to.

• Update docker/setup-buildx-action digest to 885d146 by @renovate in #776
• Update alpine Docker tag to v3.18.3 by @renovate in #817
• Update actions/checkout digest to f43a0e5 by @renovate in #860
• Update kubernetes packages to v0.28.1 by @renovate in #832
• Update actions/setup-go digest to 93397be by @renovate in #818
• Update actions/checkout action to v4 by @renovate in #863
• Update actions/upload-artifact digest to a8a3f3a by @renovate in #867
• Update actions/cache digest to 704facf by @renovate in #869
• Update docker/setup-buildx-action action to v3 by @renovate in #872
• Update docker/setup-qemu-action action to v3 by @renovate in #873
• feat(meta.pkg): set to v1 by @haarchri in #882
• ignore cidr_block on lateinitialize to avoid conflicts when using ipam by @djeremiah in #883
• Request for REDSHIFT SERVERLESS resource by @svscheg in #802
• Add reference for Configuration to kafka cluster by @mbbush in #877
• Fix copy-paste errors in Configure comments by @mbbush in #878
• Update actions/checkout digest to 8ade135 by @renovate in #891
• Add option to skip region validation by @carpenterm in #814
• Adding aws_msk_scram_secret_association to v1beta1 by @mbbush in #836
• Add docs for family providers by @turkenf in #893
• Add ability to publish family provider docs for updoc workflow by @turkenf in #880
• Adding aws_batch_job_definition to v1beta1 version by @huffmanjohnf in #857
• Configure a default poll jitter for the controllers by @ulucinar in #896
• Regenerate batch.JobDefinition by @ulucinar in #899

New Contributors

• @mbbush made their first contribution in #877
• @huffmanjohnf made their first contribution in #857

Full Changelog: v0.40.0...v0.41.0

v.0.40.0

What's Changed

Important

Provider version 0.40 introduced a regression (see #929) related to IAM roles and role policy attachments. The issue was fixed in provider version 0.43.0. If you haven't installed versions 0.40.0, 0.41.0 or 0.42.0 into your cluster, we recommend skipping those releases and upgrading directly to 0.43.0 when you choose to upgrade. If you have installed one of the affected releases, we recommend upgrading to an unaffected release (0.43+), and then you will need to unset the spec.forProvider.managedPolicyArns value from any Role.iam.aws.upbound.io managed resources that you want to be able to use RolePolicyAttachment resources to attach policies to.

• Fix warning title for monolithic provider by @turkenf in #848
• Ability to define roles with inline policy in the iam.Role resource by @turkenf in #745
• Configure iam.RolePolicy resource and add example manifest by @turkenf in #770
• fix(lateinit): skip version_id for firehose deliverystream by @haarchri in #852

Full Changelog: v0.39.0...v0.40.0

v0.39.0

What's Changed

• Change spec.owner in catalog-info.yaml by @Piotr1215 in #822
• Configure and add example for PrincipalAssociation.ram and ResourceShareAccepter.ram by @turkenf in #819
• Add warning for monolithic provider to the docs by @turkenf in #824
• Inherit golangci-lint version from build submodule by @ytsarev in #829
• Add targetgroupArnRef by @mhoshi-vm in #831
• ci: scheduled trivy scan by @phisco in #608
• Bump Terraform CLI to v1.5.5 by @ulucinar in #837
• Bump upjet to commit bd528e443b6f by @ulucinar in #838
• Bump alpine base image to v3.18.3 by @ulucinar in #839
• Bump upjet to commit e620c6228964 by @ulucinar in #843
• Bump upjet to v0.10.0 by @ulucinar in #845

New Contributors

• @mhoshi-vm made their first contribution in #831

Full Changelog: v0.38.0...v0.39.0