-
Notifications
You must be signed in to change notification settings - Fork 637
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.needs-prioritytriage/unresolvedIndicates an issue that can not or will not be resolved.Indicates an issue that can not or will not be resolved.
Description
/kind feature
Describe the solution you'd like
SubnetSpec 'ID' must not be required field
Anything else you would like to add:
I tested creating aws managed control plane with configuring specific subnet cidr.
When I tested it 21 days ago, it worked fine.
And today, I tested same thing but it require subnet's ID, so test was failed.
I found pull request about this, and realize that subnet id is no longer omitempty.
pull/3748
Subnet id must be required only when using 'Bring Your Own AWS Infrastructure'
Environment:
- Cluster-api-provider-aws version:
- Kubernetes version: (use
kubectl version): - OS (e.g. from
/etc/os-release):
anmolsachan
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.needs-prioritytriage/unresolvedIndicates an issue that can not or will not be resolved.Indicates an issue that can not or will not be resolved.