You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📝 docs(README): add instructions for using multiple subnets
- provide examples for specifying multiple subnet IDs and names
- update documentation to guide users on using multiple subnets with NodeENI
✨ feat(controller): support multiple subnets for ENI creation
- introduce new fields `subnetIDs` and `subnetNames` in CRD
- add logic to select a subnet from provided IDs or names
- enhance flexibility in ENI creation by allowing multiple subnet options
♻️ refactor(controller): extract subnet ID determination logic
- create `determineSubnetID` function for clearer subnet selection process
- improve code readability by separating subnet logic from ENI creation
📝 docs(crds): update CRD documentation for subnet enhancements
- document new `subnetIDs` and `subnetNames` fields in CRD YAML
- clarify usage scenarios for multiple subnets in ENI configuration
✨ feat(samples): add sample configurations for multiple subnets
- include new YAML samples demonstrating usage of multiple subnet IDs and names
- provide practical examples for users to reference when configuring ENIs
Copy file name to clipboardExpand all lines: README.md
+44Lines changed: 44 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -310,6 +310,50 @@ If you prefer to deploy manually:
310
310
description: "Multus ENI for secondary network interfaces"
311
311
```
312
312
313
+
### Using Multiple Subnets
314
+
315
+
You can specify multiple subnets in your NodeENI resource. The controller will selectone of the subnets to create the ENI:
316
+
317
+
```yaml
318
+
apiVersion: networking.k8s.aws/v1alpha1
319
+
kind: NodeENI
320
+
metadata:
321
+
name: multi-subnet-eni
322
+
spec:
323
+
nodeSelector:
324
+
ng: multi-eni
325
+
# Specify multiple subnet IDs - one will be selected
326
+
subnetIDs:
327
+
- subnet-0f59b4f14737be9ad # Replace with your subnet ID
328
+
- subnet-abcdef1234567890 # Replace with your subnet ID
329
+
securityGroupIDs:
330
+
- sg-05da196f3314d4af8 # Replace with your security group ID
331
+
deviceIndex: 1
332
+
deleteOnTermination: true
333
+
description: "ENI with multiple subnet options"
334
+
```
335
+
336
+
You can also use subnet names instead of IDs:
337
+
338
+
```yaml
339
+
apiVersion: networking.k8s.aws/v1alpha1
340
+
kind: NodeENI
341
+
metadata:
342
+
name: multi-subnet-name-eni
343
+
spec:
344
+
nodeSelector:
345
+
ng: multi-eni
346
+
# Specify multiple subnet names - one will be selected
347
+
subnetNames:
348
+
- eks-private-subnet-1
349
+
- eks-private-subnet-2
350
+
securityGroupIDs:
351
+
- sg-05da196f3314d4af8 # Replace with your security group ID
352
+
deviceIndex: 2
353
+
deleteOnTermination: true
354
+
description: "ENI with multiple subnet name options"
355
+
```
356
+
313
357
### Automatically Bringing Up Secondary Interfaces
314
358
315
359
When AWS attaches a secondary ENI to an EC2 instance, the interface is visible to the operating system but typically in a DOWN state. To automatically bring these interfaces up:
0 commit comments