Closed james-masson closed 6 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Is your feature request related to a problem?
As a Kubernetes admin, running clusters for development use, I would like to ensure that developers have a safe default of front-end security group rules for development services.
Describe the solution you'd like
A configuration option via https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.6/deploy/configurations/
... that sets a default equivalent of the annotations
service.beta.kubernetes.io/aws-load-balancer-security-groups
andalb.ingress.kubernetes.io/security-groups
... where the security group itself is provided by an external source.
Describe alternatives you've considered
Current best available solution is requiring devs to add a well-known SG name into the above annotations, and managing compliance through Git flow.