IAM Roles for Service Accounts ( IRSA) enables you to associate an IAM role with a Kubernetes service account, and follow the principle of least privilege by giving pods only the AWS API permissions they need, without sharing permissions to all pods running on the same node. If you are interested in working on this issue or have submitted a pull request, please leave a comment.Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request.Please vote on this issue by adding a :+1: reaction to the original issue to help the community and maintainers prioritize this request.Ordered_placement_strategy = local.ordered_placement_strategy Task_memory = module.global_fault_task_memory Security_group_ids = ĭeployment_minimum_healthy_percent = module.global_fault_deployment_minimum_healthy_percentĭeployment_maximum_percent = module.global_fault_deployment_maximum_percentĭeployment_controller_type = module.global_fault_deployment_controller_type Launch_type = module.global_fault_ecs_launch_type Stage = module.global_settings.environmentĬontainer_definition_json = ntainer_nsitive_json_map_encoded_listĪlb_security_group = var.security_group_idĮcs_load_balancers = local.ecs_load_balancer_configĬapacity_provider_strategies = var.capacity_provider_strategies Source = "cloudposse/ecs-alb-service-task/aws"
0 kommentar(er)
