@pulumi/eks 0.41.3-alpha.1659956732 → 0.41.3-alpha.1662465307
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/cluster.d.ts +1 -1
- package/cmd/provider/schema.json +1 -1
- package/package.json +1 -1
- package/package.json.dev +1 -1
package/cluster.d.ts
CHANGED
|
@@ -214,7 +214,7 @@ export interface ClusterOptions {
|
|
|
214
214
|
* and/or `privateSubnetIds` is mutually exclusive. The use of
|
|
215
215
|
* `publicSubnetIds` and `privateSubnetIds` is encouraged.
|
|
216
216
|
*
|
|
217
|
-
* Also consider setting `nodeAssociatePublicIpAddress:
|
|
217
|
+
* Also consider setting `nodeAssociatePublicIpAddress: false` for
|
|
218
218
|
* fully private workers.
|
|
219
219
|
*/
|
|
220
220
|
privateSubnetIds?: pulumi.Input<pulumi.Input<string>[]>;
|
package/cmd/provider/schema.json
CHANGED
|
@@ -783,7 +783,7 @@
|
|
|
783
783
|
"items": {
|
|
784
784
|
"type": "string"
|
|
785
785
|
},
|
|
786
|
-
"description": "The set of private subnets to use for the worker node groups on the EKS cluster. These subnets are automatically tagged by EKS for Kubernetes purposes.\n\nIf `vpcId` is not set, the cluster will use the AWS account's default VPC subnets.\n\nWorker network architecture options:\n - Private-only: Only set `privateSubnetIds`.\n - Default workers to run in a private subnet. In this setting, Kubernetes cannot create public, internet-facing load balancers for your pods.\n - Public-only: Only set `publicSubnetIds`.\n - Default workers to run in a public subnet.\n - Mixed (recommended): Set both `privateSubnetIds` and `publicSubnetIds`.\n - Default all worker nodes to run in private subnets, and use the public subnets for internet-facing load balancers.\n\nSee for more details: https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html.Note: The use of `subnetIds`, along with `publicSubnetIds` and/or `privateSubnetIds` is mutually exclusive. The use of `publicSubnetIds` and `privateSubnetIds` is encouraged.\n\nAlso consider setting `nodeAssociatePublicIpAddress:
|
|
786
|
+
"description": "The set of private subnets to use for the worker node groups on the EKS cluster. These subnets are automatically tagged by EKS for Kubernetes purposes.\n\nIf `vpcId` is not set, the cluster will use the AWS account's default VPC subnets.\n\nWorker network architecture options:\n - Private-only: Only set `privateSubnetIds`.\n - Default workers to run in a private subnet. In this setting, Kubernetes cannot create public, internet-facing load balancers for your pods.\n - Public-only: Only set `publicSubnetIds`.\n - Default workers to run in a public subnet.\n - Mixed (recommended): Set both `privateSubnetIds` and `publicSubnetIds`.\n - Default all worker nodes to run in private subnets, and use the public subnets for internet-facing load balancers.\n\nSee for more details: https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html.Note: The use of `subnetIds`, along with `publicSubnetIds` and/or `privateSubnetIds` is mutually exclusive. The use of `publicSubnetIds` and `privateSubnetIds` is encouraged.\n\nAlso consider setting `nodeAssociatePublicIpAddress: false` for fully private workers."
|
|
787
787
|
},
|
|
788
788
|
"providerCredentialOpts": {
|
|
789
789
|
"$ref": "#/types/eks:index:KubeconfigOptions",
|
package/package.json
CHANGED
package/package.json.dev
CHANGED