mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-28 22:18:52 +00:00
Change tab indentations to space indentations
This commit is contained in:
@@ -12,17 +12,17 @@ import TabItem from '@theme/TabItem';
|
||||
|
||||
# Changes in v2.5.8
|
||||
|
||||
- We now support private GKE clusters. Note: This advanced setup can require more steps during the cluster provisioning process. For details, see [this section.](../reference-guides/cluster-configuration/rancher-server-configuration/gke-cluster-configuration/gke-private-clusters.md)
|
||||
- [Shared VPCs](https://cloud.google.com/vpc/docs/shared-vpc) are now supported.
|
||||
- We now support more configuration options for Rancher managed GKE clusters:
|
||||
- Project
|
||||
- Network policy
|
||||
- Network policy config
|
||||
- Node pools and node configuration options:
|
||||
- More image types are available for the nodes
|
||||
- The maximum number of pods per node can be configured
|
||||
- Node pools can be added while configuring the GKE cluster
|
||||
- When provisioning a GKE cluster, you can now use reusable cloud credentials instead of using a service account token directly to create the cluster.
|
||||
- We now support private GKE clusters. Note: This advanced setup can require more steps during the cluster provisioning process. For details, see [this section.](../reference-guides/cluster-configuration/rancher-server-configuration/gke-cluster-configuration/gke-private-clusters.md)
|
||||
- [Shared VPCs](https://cloud.google.com/vpc/docs/shared-vpc) are now supported.
|
||||
- We now support more configuration options for Rancher managed GKE clusters:
|
||||
- Project
|
||||
- Network policy
|
||||
- Network policy config
|
||||
- Node pools and node configuration options:
|
||||
- More image types are available for the nodes
|
||||
- The maximum number of pods per node can be configured
|
||||
- Node pools can be added while configuring the GKE cluster
|
||||
- When provisioning a GKE cluster, you can now use reusable cloud credentials instead of using a service account token directly to create the cluster.
|
||||
|
||||
# Cluster Location
|
||||
|
||||
|
||||
Reference in New Issue
Block a user