Hi @ana-aguilar7. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign rifelpet for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

/ok-to-test

/test pull-kops-verify-generated

/retest-required

/retest

/test pull-kops-e2e-aws-upgrade-k133-ko133-to-klatest-kolatest-many-addons

@ana-aguilar7 please ignore that test for now.

@ana-aguilar7 instead of creating a new integration test, could you add the new options to t the following tests?

many-addons-ccm
many-addons-ccm-irsa

/test pull-kops-e2e-aws-upgrade-k133-ko133-to-kstable-kolatest-many-addons

/retest

@ana-aguilar7 Please rebase, needed to grab the latest change to pass the netlify tests.
Also, you need to run make apimachinery crds and add the output to the PR.
Other than that, this LGTM.

@ana-aguilar7: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

@ana-aguilar7 I think you are still missing a few files from hack/update-expected.sh.