terraform-aws-eks-blueprints icon indicating copy to clipboard operation
terraform-aws-eks-blueprints copied to clipboard

Published 20 hours ago • verified publisher icon aws-ia

[FEATURE] `teams` next design iteration

Open bryantbiggs opened this issue 3 years ago • 4 comments
trafficstars

Is your feature request related to a problem? Please describe

  • This issue will be used to collect feedback and share direction on the next iteration of the teams module and its functionality.

Proposed Changes

  • Support n number of namespaces per team
  • Support n number of teams - currently application_team and platform_team
    • We can provide a default with the current two teams, but allow users to also specify additional teams
  • Support for using as standalone module
  • Support for limit ranges

Additional context

  • #433
  • #647
  • #691
  • #975

bryantbiggs avatar Aug 11 '22 18:08 bryantbiggs

Interested in this feature but could you also consider adding the following scenario as well? It would be beneficial for an environment where namespace access is not locked into being managed by a single team.

  • Support namespaces that can be accessed/controlled by multiple teams

mikeinton avatar Oct 03 '22 17:10 mikeinton

Have consider in addition of quotas for the namespace, also support limitranges? Bad idea or good idea?

csantanapr avatar Oct 05 '22 17:10 csantanapr

Have consider in addition of quotas for the namespace, also support limitranges? Bad idea or good idea?

Agree that we would also make use of limitranges if they were available here as well.

mikeinton avatar Oct 06 '22 22:10 mikeinton

@bryantbiggs I am looking forward to completing this feature.

Hokwang avatar Nov 07 '22 04:11 Hokwang

here is an early look at proposed changes for the next iteration of the teams module https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/refactor/v5-part-deux/modules/kubernetes-team

bryantbiggs avatar Feb 06 '23 12:02 bryantbiggs

is there any update on the status of this refactor? My team is working on building our internal k8s platform and we want to use these blueprints as the basis of the project. We have the EKS cluster up and running, but are wondering what is the current recommendation for setting up teams and users? Should we continue with the older aws-eks-teams module and migrate once v5 is released? Or should we stand up our teams with the new kubernetes_team module on this branch?

jasondewitt avatar Mar 06 '23 19:03 jasondewitt

this is now available here https://github.com/aws-ia/terraform-aws-eks-blueprints-teams - we will continue to support the current implementation here and will provide an upgrade/migration guide before removing it from the project

bryantbiggs avatar Mar 17 '23 13:03 bryantbiggs