Getting started with Kubernetes is often harder than it needs to be. While working with a cluster “from scratch” can be a great learning exercise or a good solution for some highly specialized workloads, often the details of cluster management can be made easier by utilizing a managed service offering. Google Kubernetes Engine (GKE) allows for an easier end-to-end developer experience with convenient tooling and built-in integrations along with the convenience of offering Kubernetes clusters as a managed service.

GKE is the most mature container orchestration service available today, delivering a fully-managed service and hands-off experience with the GKE Autopilot mode of operation. GKE provides industry-first capabilities such as release channels, multi-cluster support, unique four-way auto scaling, node auto repair, and can support up to 15K nodes in a single cluster. 

Our modern, end-to-end platform is built on cloud-native principles you are already familiar with and prioritizes speed, security, and flexibility, in ways that are highly differentiated from other cloud platforms. 

We have put together a new reference guide for you as you begin your journey developing on GKE. It covers every step of your journey from writing, running, operating, to managing code. Even if it isn’t your first time using GKE, this e-book will be a valuable resource highlighting important considerations and best practices. By implementing the technical recommendations, following the steps, and utilizing the tools described, you can reach the following goals:

• Write, deploy, and debug code faster with Cloud Code and Cloud Shell
• Continuously integrate and deliver updates with Cloud Build
• Run easily, securly, cost effectively at scale with GKE
• Monitor and troubleshoot with Google Cloud’s operations suite 

Kick-start your journey by downloading the e-book and join us live June 22 at 9am PDT for our half-day Cloud OnBoard event: Getting Started with Google Kubernetes Engine. 

It’s been quite a year. In general, and for work. Just the other day, I read a new study from Pew Research that shows 71% of people are currently working from home, and 50% of employees say they want to continue working from home at least three days a week. That’s more than half of people wanting to be remote over half the time!

As we’ve been navigating our own return to the office here at Google, one thing has become more clear than ever: the browser is no longer just a portal to the internet—it’s one of the most critical components of our tech stack. And we know we’re not alone in this. As our organization, and other organizations of all sizes, transition to a more hybrid way of working, it’s absolutely key to have a modern browser that’s built to support both admins and end users. 

The good news is, Chrome is made for this! Literally. It’s purpose-built for flexible work—and as the future unfolds and businesses’ needs continue to evolve, we’re committed to making sure our browser is even easier to manage, even more secure, and even more helpful, so all of us can be more productive. 

What’s next for Chrome

As we design and build Chrome to be a stronger asset for the enterprise, we are focused on these key areas:

1. Simple management
2. Modernized security 
3. Productivity enhancements 
4. Helpful integrations 

We’ve already made great strides in all four areas, with more exciting releases to come soon. Let’s take a closer look at what’s new and available right now, what to look forward to, and how each feature is equipping Chrome browser-based businesses (and their users) for what’s next.

When it comes to simple management there have been a lot of exciting developments—Chrome Browser Cloud Management is built for this new hybrid reality, giving IT teams the advantage of powerful and flexible management capabilities both in the cloud and on premises, so they always have the visibility and insights they need to make more informed decisions, quickly. 

With recent new releases admins can:

1. Track all versions of Chrome from one place. Our new daily version report allows IT teams to see all versions, including minor versions, in a single report to support compliance and make it easier to see and manage their entire deployment.
2. Report on apps and extensions across the organization. A new Apps & Usage report provides helpful visibility into all installed extensions, Progressive Web Apps (PWAs), Chrome apps, and Android apps. You can see versions and permissions for each individual app and even force install or block, right from the report. 
3. Remotely troubleshoot and clear browser data. This is one of my favorites because not only is it incredibly helpful, it was created from customer requests! Admins (and a lot of service desk employees) told us how useful it would be if they could clear an end user’s browsing data, cookies, and cache remotely – and our team made it happen.
4. Extension management improvements. Coming this summer: extension request workflow will empower admins to change the behavior of Chrome Web Store so that end users request extensions and admins then approve or deny the installations from a centralized list in Admin Console. Another new release is extension details, where admins can now find out exactly what extensions are installed where, who makes them, what resources they’re using, and all other extension-related details – also right from the Admin console.  

Of all of our priorities, modernized security often feels most urgent. In a recent security report, 65% of US and UK employees said they received a phishing email during the remote working period initiated by COVID-19.  Further, a study by the Ponemon Institute found that 41% of responding organizations had dealt with an attack involving the compromise of employees’ passwords, costing an average of $267,408 per organization. Between the regular emergence of new threats and the increase in targeted mobile attacks, our new ways of working definitely demand a fresh approach to security. 

• BeyondCorp Enterprise, our new modern zero trust solution, enables secure access to critical apps and services with integrated threat and data protection, all delivered through Chrome browser, was introduced in January 2021. Its agentless approach simplifies the admin and end-user experience. We also just launched BeyondCorp Enterprise protected profiles to help organizations protect their extended workforce, including contractors, frontline workers, and anyone working from home who needs to securely access corporate resources from shared or unmanaged devices. 

To learn more about Google’s approach to modernizing security, tune into the Wall Street Journal’s Advancing Security in the New Business Environment event tomorrow from 10:35 am – 10:55 am EST, with very own Parisa Tabriz (Head of Chrome Engineering, Product Management and UX) and Phil Venables (CISO of Google Cloud). 

When it comes to productivity enhancements, I’m proud to share that we’re consistently releasing features that support users no matter where they’re working. Now that the browser is where so much of our day-to-day work happens, it’s more important than ever before to build in new ways to save time and work together while apart. 

Recently released productivity-boosting features include:

1. A faster way to take action right from the address bar. Chrome Actions is a feature we launched last year,  where you can simply type in commands such as “clear browsing data ” or “open incognito window”and get down to business in just a few clicks. We’re excited to announce new Chrome Actions are now available through our beta channel! Try one of these actions to check it out: “ Run Chrome safety check,” “Create doc,” and “Manage Google Account.”
2. Link directly to highlighted text. If you like to share snippets and quotes from articles or websites with your colleagues, you’re in luck. Now, instead of sharing the URL link from the address bar, you can take advantage of the new “link to highlight” feature in Chrome to point to the specific content. Simply choose the content you want to share, right click, select “Copy link to highlight,” and then send the link – to the exact part of the page you want people to see. It’s available for desktop and Android now, and coming soon for iOS. 
3. Decreased Chrome CPU usage. This means more battery life, less heat coming off of your device, and less fan noise. 🎉 🙌🏻
4. And there’s more! To explore additional productivity features, check out this blog post. 

Our final area of focus is all about giving Chrome customers more choice with helpful integrations. We’re actively partnering with best-of-breed organizations to bring integrations —and your favorite tools— into Chrome, to create a more seamless and productive experience across the board. Stay tuned on this as we’ll have more to share later this year. In the meantime, hear from our Modern Computing Alliance partners, such as Box, HP, RingCentral, Okta and VMware, as they explore many of the most important questions about returning to the office.

We’re constantly thinking about how we can help people and organizations adapt and thrive as they begin to return to the office. See below for three events from the team that cover how to make the transition to hybrid easier for your team, be sure to check them out.

Modernizing Your Approach to Security session at the Wall Street Journal’s Advancing Security in the New Business Environment event

• Tomorrow June 2, 2021
• 10:35 – 10:55 AM EST
• Register here

Chrome Insider: Browser tips & tricks for IT admins

• June 10, 2021
• 10:00 AM  – 11:15 PT
• Register here

Editor’s note: Today we hear from ForgeRock, a multinational identity and access management software company with more than 1,100 enterprise customers, including a major public broadcaster. In total, customers use the ForgeRock Identity Platform to authenticate and log in over 45 million users daily, helping them manage identity, governance, and access management across all platforms, including on-premises and multicloud environments. 

Operating at that kind of scale isn’t easy. In this blog post, ForgeRock Engineering Director, Warren Strange discusses the three things that help make their developers efficient and productive, and the Google Cloud tools they use along the way. 

At ForgeRock, we’ve been an early adopter of Kubernetes, viewing it as a strategic platform. Running on Kubernetes allows us to drive multicloud support across Google Kubernetes Engine (GKE), Amazon (EKS), and Azure (AKS). So no matter which cloud our customers are running on, we are able to seamlessly integrate our products into customers’ environments. 

Making it easier for ForgeRock’s developers and operators to build, deploy and manage applications has been crucial in our ability to continually provide high quality solutions for our customers. We’re always looking for tools to improve productivity and keep our developers focused on coding instead of configuration. Google Cloud’s suite of DevOps tools have streamlined three specific practices to help keep our developers productive: 

1. Make developers productive within IDEs

Developer productivity is core to the success of any organization, including ForgeRock. Since developers spend most of their time within their IDE of choice, our goal at ForgeRock has been to make it easier for our developers to write Kubernetes applications within the IDEs they know and love. Cloud Code helps us precisely with that: it makes the process of building, deploying, scaling, and managing Kubernetes infrastructure and applications a breeze. 

In particular, working with the Kubernetes YAML syntax and schema takes time, and a lot of trial and error to master. Thanks to YAML authoring support within Cloud Code, we can easily avoid the complicated and time consuming task of writing YAML files at ForgeRock. With YAML authoring support, developers save time on every bug. Cloud Code’s inline  snippets, completions, and schema validation, a.k.a. “linting,” further streamline working with YAML files. 

The benefits of Cloud Code extend to local development as well. Iterating locally on Kubernetes applications often requires multiple manual steps, including building container images, updating Kubernetes manifests, and redeploying applications. Doing these steps over and over again can be a chore. Cloud Code supports Skaffold under the hood, which tracks changes as they come and automatically rebuilds and redeploys—reducing repetitive development tasks. 

Finally, developing for Kubernetes usually involves jumping between the IDE, documentation, samples etc. Cloud Code reduces this context switching with Kubernetes code samples. With samples, we can get new developers up and running quickly. They spend less time learning about configuration and management of the application—and spend more time on writing and evolving the code.

2. Drive end-to-end automation

To further improve developer productivity, we’ve focused on end-to-end automation: from writing code within IDEs, to automatically triggering CI/CD pipelines and running the code in production. In particular, Tekton, Cloud Build, Container Registry, and GKE have been critical to Forgerock as we streamline the flow of code, feedback and remediation through the build and deployment processes. The process looks something like this:

We begin by developing Kubernetes manifests and dockerfiles using Cloud Code. Then we use Skaffold to build containers locally, while Cloud Build helps with continuous integration (CI). The Cloud Build GitHub app allows us to automate builds and tests as part of our GitHub workflow. Cloud Build is differentiated from other continuous integration tools since it is fully serverless. It scales up and scales down in response to load, with no need for us to pre-provision servers or pay in advance for additional capacity. We pay for the exact resources we use. 

Once the image is built by Cloud Build, it is stored, managed, and secured in Google’s Container Registry. Just like Cloud Build, Container Registry is serverless, so we only pay for what we  use. Additionally, since Container Registry comes with automatic vulnerability scanning, every time we upload a new image to Container Registry, we can also scan it for vulnerabilities. 

Next, a Tekton pipeline is triggered, which deploys the docker images stored in Container Registry and Kubernetes manifests to a running GKE cluster. Along with Cloud Build, Tekton is a critical part of our CI/CD process at ForgeRock. Most importantly, since Tekton comes with standardized Kubernetes-native primitives, we can create continuous delivery workflows very quickly.

After deployment, Tekton triggers a functional test suite to ensure that the applications we deploy perform as expected. The test results are posted to our team Slack channel so all developers have instant access and insights about each cluster. From there, we are able to provide our customers with their finished product request.

3.  Leverage multicloud patterns and practices

The industry has seen a shift towards multicloud. Organizations have adopted multicloud strategies to minimize vendor lock-in, take advantage of best-in-class solutions, improve cost-efficiencies, and increase flexibility through choice. 

At ForgeRock, we’re big proponents of multicloud. Part of that comes from the fact that our identity and access management product works across Google Cloud, AWS, and Azure. Developing products using open-source technologies such as Kubernetes has been particularly helpful in driving this interoperability. 

Tekton has been another critical project that has allowed us to prevent vendor lock-in. Thanks to Tekton, our continuous delivery pipelines can deploy across any Kubernetes cluster. Most importantly, since Tekton pipelines run on Kubernetes, these pipelines can be decoupled from the runtime. Like Tekton and Kubernetes, both Cloud Build and Container Registry are based on open technologies. Community-contributed builders and official builder images allow us to connect to a variety of tools as a part of the build process. And finally, with support for open technologies like Google Cloud buildpacks within Cloud Build, we can build containers without even knowing Docker. 

Making it easier for developers and operators to build, deploy and manage applications is critical for the success of any organization. Driving developer productivity within IDEs, leveraging end-to-end automation, and support for multi-cloud patterns and practices are just some of the ways we are trying to achieve this at ForgeRock. To learn more about ForgeRock, and to deploy the ForgeRock Identity Platform into your Kubernetes cluster, check out our open-source ForgeOps repository on GitHub.

Many of the world’s leading companies run on SAP—and deploying it on Google Cloud extends the benefits of SAP even further. Migrating your current SAP S/4HANA deployment to Google Cloud—whether it resides on your company’s on-premises servers or another cloud service—provides your organization with a flexible virtualized architecture that lets you scale your environment to match your workloads, so you pay only for the compute and storage capacity you need at any given moment. Google Cloud includes built-in features, such as Compute Engine live migration and automatic restart, that minimize downtime for infrastructure maintenance. And it allows you to integrate your SAP data with multiple data sources and process it using Google Cloud technology such as BigQuery to drive data analytics.

SAP server-side architecture consists of two layers: the SAP HANA database, and the Netweaver application layer. In this blog post, we’ll look at the options and steps for moving the database layer to Google Cloud as a lift and shift or rehost, a straightforward approach that entails moving your current SAP environment unchanged onto Google Cloud.

Deploying an SAP HANA system on Google Cloud

Google Cloud offers SAP-certified virtual machines (VMs) optimized for SAP products, including SAP HANA and SAP HANA Enterprise Cloud, as well as dedicated servers for SAP HANA for environments greater than 12TB. (For a complete list of VM and hardware options, visit the Certified and Supported SAP HANA Hardware Directory.)

Before proceeding with a rehost migration to Google Cloud, your current (source) environment and Google Cloud (target) environments should meet these specifications:

Prerequisites:  

• The configuration of the Google Cloud environment (i.e., VM  resources, SSD storage capacity) should be identical to that of the source environment. If the underlying hardware is different, however, you must use Option 2 for your migration, detailed below.
• Both environments should be running the same operating system (SUSE or RHEL Linux).
• The HANA version, instance number, and system ID (SID) should be identical.

• Schema names must remain the same.
• Establishing the network connection between the on-premises environment and Google Cloud will be required in this phase to support rehost of the SAP application.you can use Cloud VPN or Dedicated Interconnect. Learn more about Dedicated Interconnect and Cloud VPN.

Note: Depending on your internet connection and bandwidth requirements, we recommend using a Dedicated Interconnect over Cloud VPN for production environments. 

We offer a number of automated processes to accelerate your cloud journey. To deploy the SAP HANA system on Google Cloud, you can use the Google Cloud Deployment manager or Terraform and Ansible scripts available on GitHub with configuration file templates to define your installation. For more details, see the Google Cloud SAP HANA Planning Guide.

Note: To deploy SAP HANA on Google Cloud machine types that are certified by SAP for production, please review the Certification for SAP HANA on Google Cloud page. 

Moving an SAP HANA Database to Google Cloud

There are two different options you can use to rehost your SAP HANA database to Google Cloud, and each has pros and cons that you should consider when deciding on your approach.

Option 1: Asynchronous replication uses SAP’s built-in replication tool to provide continuous data replication from the source system (also known as the primary system) to the destination or secondary system—in this case residing on Google Cloud. It’s best for mission-critical applications for which minimum downtime is a high priority, and for large databases. In addition, the high level of automation means that the process requires less manual intervention. Here’s where you can learn more on HANA Asynchronous Replication.

Option 2: Backup and restore relies on SAP’s backup utility to create an image of the database that is then transferred to Google Cloud, where it is restored in the new environment. Downtime for this method varies by database size, so large databases may require more downtime via this method vs. asynchronous replication. It also involves more manual tasks. However, it requires fewer resources to perform, making it an attractive option for less urgent use cases. Here’s where you can learn more on SAP HANA database Backup and restore.

How to migrate the SAP HANA database to Google Cloud using Asynchronous Replication

1. Create and configure Dedicated Interconnect or Cloud VPN between the current environment and Google Cloud.
2. Set up SAP HANA asynchronous replication. You can configure system replication using SAP HANA Cockpit, SAP HANA Studio, or hdbnsutil. See Setting Up SAP HANA System Replication in the SAP HANA Administration Guide.
3. Be sure to use the same instance number and HANA SID in the template as the primary instance.
4. Configure the Google Cloud instance as the secondary node for using HANA Asynchronous replication.
5. Perform data validation once full data replication is completed to the SAP HANA database in Google Cloud. To learn more: HANA System Replication overview.  
6. Perform an SAP HANA takeover on your standby database. This switches your active system from the current primary system onto the secondary system on Google Cloud. Once the takeover command runs, the system on Google Cloud becomes the new primary system.To learn more: HANA Takeover. 

How to migrate the SAP HANA database to Google Cloud using Backup and Restore

1. Create a full backup of your SAP HANA database in your current environment.
2. Create a new storage bucket in your Google Cloud environment. Visit Creating Storage Buckets in the Google Cloud Storage documentation. 
3. Download and install gsutil onto the source environment and run it to upload the HANA backup to the Google Cloud storage bucket. To install gsutil utility on any computer or server, visit Install gsutil in the Google Cloud Storage documentation.
   Note: You can run parallel multi thread/multi processing in gsutil to copy large files more quickly.
4. Recover the HANA database on Google Cloud using SAP’s RECOVER DATABASE statement. See RECOVER DATABASE Statement (Backup and Recovery) in the SAP HANA SQL Reference Guide for SAP HANA Platform.

Note: BackInt agent is an integrated SAP interface tool used for HANA database on Google Cloud.Backint agent for SAP HANA can be used to store and retrieve backups directly from Google Cloud Storage. It is supported and certified by SAP on Google Cloud. To learn more:  SAP HANA Backint Agent on Google Cloud. 

In summary, we recommend using Asynchronous Replication (Option 1) for mission-critical applications that require the lowest downtime window. For all other applications, we recommend Backup and Restore (Option 2), as this approach requires fewer resources. It’s also a great way to implement the backup and restore functionality on Google Cloud.

A rehost migration is the most straightforward path to getting your SAP on HANA system up and running on Google Cloud. And the sooner you migrate, the sooner you can take advantage of the many benefits Google Cloud brings to your SAP solution. For more information on the different migration options please review: SAP on Google Cloud: Migration strategies. 

Learn more about deploying SAP on Google Cloud. Technical resources can be found here.