From e3588b105f994414dabbd1b72e12119c6720e285 Mon Sep 17 00:00:00 2001 From: Daniel Sanche Date: Mon, 19 Oct 2020 16:47:50 -0700 Subject: [PATCH] use Kubernetes Engine branding --- docs/handlers-container-engine.rst | 4 ++-- docs/usage.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/handlers-container-engine.rst b/docs/handlers-container-engine.rst index a0c6b2bc..5286ec58 100644 --- a/docs/handlers-container-engine.rst +++ b/docs/handlers-container-engine.rst @@ -1,5 +1,5 @@ -Google Container Engine Log Handler -=================================== +Google Kubernetes Engine Log Handler +==================================== .. automodule:: google.cloud.logging.handlers.container_engine :members: diff --git a/docs/usage.rst b/docs/usage.rst index a9af1164..4714144f 100644 --- a/docs/usage.rst +++ b/docs/usage.rst @@ -336,7 +336,7 @@ logging handler can use different transports. The default is direct API call on each logging statement to write the entry. -.. _Google Container Engine: https://cloud.google.com/container-engine/ +.. _Google Kubernetes Engine: https://cloud.google.com/kubernetes-engine fluentd logging handlers ~~~~~~~~~~~~~~~~~~~~~~~~ @@ -347,7 +347,7 @@ which writes directly to the API, two other handlers are provided. recommended when running on the Google App Engine Flexible vanilla runtimes (i.e. your app.yaml contains ``runtime: python``), and :class:`~google.cloud.logging.handlers.container_engine.ContainerEngineHandler` -, which is recommended when running on `Google Container Engine`_ with the +, which is recommended when running on `Google Kubernetes Engine`_ with the Cloud Logging plugin enabled. :meth:`~google.cloud.logging.client.Client.get_default_handler` and