Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Update cluster autoscaler policy for recent permission changes upstream #255

Conversation

bryantbiggs
Copy link
Member

@bryantbiggs bryantbiggs commented Jun 1, 2022

Description

  • Update cluster autoscaler policy for recent permission changes upstream
  • Update documentation for recent v5 changes

Motivation and Context

  • Align with upstream addons permission changes

Breaking Changes

  • No

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@antonbabenko antonbabenko merged commit 2f1b2bf into terraform-aws-modules:master Jun 1, 2022
@bryantbiggs bryantbiggs deleted the feat/update-cluster-autoscaler branch June 1, 2022 15:35
antonbabenko pushed a commit that referenced this pull request Jun 1, 2022
## [5.1.0](v5.0.0...v5.1.0) (2022-06-01)

### Features

* Update cluster autoscaler policy for recent permission changes upstream ([#255](#255)) ([2f1b2bf](2f1b2bf))
@antonbabenko
Copy link
Member

This PR is included in version 5.1.0 🎉

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants