advancewqp.blogg.se

Otherwise, unexpected behavior and data loss can occur. After your Distributed Cloud Edge deployment has been upgraded from version 1.4.0 to version 1.5.0, you must manually delete and recreate all local control plane clusters you have created with Distributed Cloud Edge version 1.4.0 or 1.4.1. For more information, see Distributed Cloud Edge survivability mode. Survivability mode is now generally available. The following changes have been introduced in this release of Distributed Cloud Edge: For more information, see Enable support for customer-managed encryption keys (CMEK) for local storage. You can now configure Cloud KMS integration for storage on nodes running local control planes for Distributed Cloud Edge clusters. This is a preview-level feature.ĬMEK support for local control plane nodes. For more information, see NodeSystemConfigUpdate resource. This allows you to specify a container image registry IP/domain pair for a network interface other than the primary. Distributed Cloud Edge now allows you to specify the network interface in the ntainerRuntimeDNSConfig field of the NodeSystemConfigUpdate resource. This is a preview-level feature.Ĭontainer image registry access over secondary networks. For more information, see Create and manage clusters. You now have the option to create a cluster running a specific version of Distributed Cloud Edge software, starting with version 1.5.0. For more information, see Configure a bastion host. The bastion host feature allows Google support engineers to connect to your Distributed Cloud Edge deployment and work with you to diagnose and resolve issues. Distributed Cloud Edge now allows you to set up one or more bastion host virtual machines. The following features have been introduced in this release of Distributed Cloud Edge:īastion host support. Save money with our transparent approach to pricing

Rapid Assessment & Migration Program (RAMP) Migrate from PaaS: Cloud Foundry, OpenshiftĬOVID-19 Solutions for the Healthcare Industry