Skip to content

v1.3.0

Latest
Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 11 Jul 23:27
· 22 commits to main since this release
1.3.0
76953f5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Enable 1 Pod Execution Role Per Cluster @Nuru (#33)

what

  • Enable 1 Pod Execution Role Per Cluster by allowing users to create either a role or a profile or both
  • Deprecate "profile role" terminology in favor of "pod execution role"
  • Update example
  • Update tests
  • Update README and workflows

why

  • All Fargate Profiles can use the same Pod Execution Role, and there is no advantage (and several disadvantages) to using a different role with each profile. This module used to always create both a profile and a role. Now it allows you to create one or the other or both.
  • The term "profile role" is confusing and suggests using one role per profile. The term "pod execution role" matches AWS documentation.
  • Example used old modules that were incompatible with AWS provider v5 and did not set ALB tags.
    • Supersedes and closes #27.
    • Supersedes and closes #31.
  • Explain 1 role per cluster. Supersedes and closes #32
Sync github @max-lobur (#29)

Rebuild github dir from the template

Contributors

Nuru and max-lobur
Assets 2
Loading