Class VPC
- java.lang.Object
-
- io.fabric8.openshift.api.model.installer.aws.v1.VPC
-
- All Implemented Interfaces:
io.fabric8.kubernetes.api.builder.Editable<VPCBuilder>,io.fabric8.kubernetes.api.model.KubernetesResource,Serializable
@Generated("io.fabric8.kubernetes.schema.generator.model.ModelGenerator") public class VPC extends Object implements io.fabric8.kubernetes.api.builder.Editable<VPCBuilder>, io.fabric8.kubernetes.api.model.KubernetesResource
VPC configures the VPC for the cluster.- See Also:
- Serialized Form
-
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description VPCBuilderedit()Map<String,Object>getAdditionalProperties()List<Subnet>getSubnets()Subnets defines the subnets in an existing VPC and can optionally specify their intended roles.voidsetAdditionalProperties(Map<String,Object> additionalProperties)voidsetAdditionalProperty(String name, Object value)voidsetSubnets(List<Subnet> subnets)Subnets defines the subnets in an existing VPC and can optionally specify their intended roles.VPCBuildertoBuilder()
-
-
-
Method Detail
-
getSubnets
public List<Subnet> getSubnets()
Subnets defines the subnets in an existing VPC and can optionally specify their intended roles. If no roles are specified on any subnet, then the subnet roles are decided automatically. In this case, the VPC must not contain any other non-cluster subnets without the kubernetes.io/cluster/<cluster-id> tag.For manually specified subnet role selection, each subnet must have at least one assigned role, and the ClusterNode, BootstrapNode, IngressControllerLB, ControlPlaneExternalLB, and ControlPlaneInternalLB roles must be assigned to at least one subnet. However, if the cluster scope is internal, then ControlPlaneExternalLB is not required.
Subnets must contain unique IDs, and can include no more than 10 subnets with the IngressController role.
Leave this field unset to have the installer create subnets in a new VPC on your behalf.
-
setSubnets
public void setSubnets(List<Subnet> subnets)
Subnets defines the subnets in an existing VPC and can optionally specify their intended roles. If no roles are specified on any subnet, then the subnet roles are decided automatically. In this case, the VPC must not contain any other non-cluster subnets without the kubernetes.io/cluster/<cluster-id> tag.For manually specified subnet role selection, each subnet must have at least one assigned role, and the ClusterNode, BootstrapNode, IngressControllerLB, ControlPlaneExternalLB, and ControlPlaneInternalLB roles must be assigned to at least one subnet. However, if the cluster scope is internal, then ControlPlaneExternalLB is not required.
Subnets must contain unique IDs, and can include no more than 10 subnets with the IngressController role.
Leave this field unset to have the installer create subnets in a new VPC on your behalf.
-
edit
public VPCBuilder edit()
- Specified by:
editin interfaceio.fabric8.kubernetes.api.builder.Editable<VPCBuilder>
-
toBuilder
public VPCBuilder toBuilder()
-
-