mirror of https://github.com/k3s-io/k3s
4220b7303e
Automatic merge from submit-queue (batch tested with PRs 36721, 46483, 45500, 46724, 46036) AWS: Allow configuration of a single security group for ELBs **What this PR does / why we need it**: AWS has a hard limit on the number of Security Groups (500). Right now every time an ELB is created Kubernetes is creating a new Security Group. This allows for specifying a Security Group to use for all ELBS **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: For some reason the Diff tool makes this look like it was way more changes than it really was. **Release note**: ```release-note ``` |
||
|---|---|---|
| .. | ||
| BUILD | ||
| OWNERS | ||
| aws.go | ||
| aws_instancegroups.go | ||
| aws_loadbalancer.go | ||
| aws_metrics.go | ||
| aws_routes.go | ||
| aws_test.go | ||
| aws_utils.go | ||
| device_allocator.go | ||
| device_allocator_test.go | ||
| log_handler.go | ||
| regions.go | ||
| regions_test.go | ||
| retry_handler.go | ||
| retry_handler_test.go | ||
| sets_ippermissions.go | ||
| tags.go | ||
| tags_test.go | ||
| volumes.go | ||