Setting up a Private Kubernetes Cluster Reviews

Juan Pablo V. · Reviewed أكثر من 7 سنوات ago

Norio N. · Reviewed أكثر من 7 سنوات ago

sourav C. · Reviewed أكثر من 7 سنوات ago

Rizwan M. · Reviewed أكثر من 7 سنوات ago

Some of your commands are deprecated: gcloud beta container clusters create private-cluster --private-cluster --master-ipv4-cidr 172.16.0.16/28 --enable-ip-alias --create-subnetwork '' WARNING: The --private-cluster flag is deprecated and will be removed in a future release. Use --enable-private-nodes instead.

Philipp W. · Reviewed أكثر من 7 سنوات ago

Fabien P. · Reviewed أكثر من 7 سنوات ago

James T. · Reviewed أكثر من 7 سنوات ago

Rik H. · Reviewed أكثر من 7 سنوات ago

Thinh H. · Reviewed أكثر من 7 سنوات ago

Phuc L. · Reviewed أكثر من 7 سنوات ago

Trevor Y. · Reviewed أكثر من 7 سنوات ago

Got these warnings: google3116757_student@cloudshell:~ (qwiklabs-gcp-16b6eaa0ec322587)$ gcloud beta container clusters create private-cluster \ > --private-cluster \ > --master-ipv4-cidr 172.16.0.16/28 \ > --enable-ip-alias \ > --create-subnetwork "" WARNING: The --private-cluster flag is deprecated and will be removed in a future release. Use --enable-private-nodes instead. WARNING: Starting in 1.12, new clusters will have basic authentication disabled by default. Basic authentication can be enabled (or disabled) manually using the`--[no-]enable-basic-auth` flag. WARNING: Starting in 1.12, new clusters will not have a client certificate issued. You can manually enable (or disable) the issuance of the client certificate using the `--[no-]issue-client-certificate` flag. WARNING: Newly created clusters and node-pools will have node auto-upgrade enabled by default. This can be disabled using the `--no-enable-autoupgrade` flag. WARNING: `--private-cluster` makes the master inaccessible from cluster-external IP addresses, by design. To allow limited access to the master, see the `--master-authorized-networks` flags and our documentation on setting up private clusters: https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters WARNING: Starting in 1.12, default node pools in new clusters will have their legacy Compute Engine instance metadata endpoints disabled by default. To create acluster with legacy instance metadata endpoints disabled in the default node pool, run `clusters create` with the flag `--metadata disable-legacy-endpoints=true`. WARNING: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation. This will enable the autorepair feature for nodes. Please see https://cloud.google.com/kubernetes-engine/docs/node-auto-repair for more information on node autorepairs. Other than that. OK. Thx

Omar G. · Reviewed أكثر من 7 سنوات ago

The lab is out of date ... in some steps it is missing --zone us-central1-a

Ahmed J. · Reviewed أكثر من 7 سنوات ago

Huy D. · Reviewed أكثر من 7 سنوات ago

Quang N. · Reviewed أكثر من 7 سنوات ago

great

Canh D. · Reviewed أكثر من 7 سنوات ago

khuong n. · Reviewed أكثر من 7 سنوات ago

Ditsayawat W. · Reviewed أكثر من 7 سنوات ago

Margaret C. · Reviewed أكثر من 7 سنوات ago

Quang D. · Reviewed أكثر من 7 سنوات ago

WARNING: The --private-cluster flag is deprecated and will be removed in a future release. Use --enable-private-nodes instead. ERROR: (gcloud.beta.container.clusters.create) One of [--zone, --region] must be supplied: Please specify location.

Trung T. · Reviewed أكثر من 7 سنوات ago

Chanh Huy V. · Reviewed أكثر من 7 سنوات ago

James W. · Reviewed أكثر من 7 سنوات ago

Jiangjun H. · Reviewed أكثر من 7 سنوات ago

Tanvir A. · Reviewed أكثر من 7 سنوات ago