Deploying and Implementing Kubernetes Engine Resources
Deploying and Implementing App Engine and Cloud Functions Resources
Deploying and Implementing Data Solutions
Deploying a Solution Using GCP Marketplace
Deploying Resources Using Deployment Manager
This course has been designed to teach you how to deploy and implement Google Cloud Platform solutions. The content in this course will help prepare you for the Associate Cloud Engineer exam.
- To learn how to deploy Kubernetes Engine resources on Google Cloud Platform
- To learn how to deploy and implement App Engine and Cloud Functions resources
- To learn how to use Cloud Launcher and Deployment Manager
- Those who are preparing for the Associate Cloud Engineer exam
- Those looking to learn more about GCP networking and compute features
To get the most from this course then you should have some exposure to GCP resources, such as Kubernetes Engine, App Engine, Cloud Functions, Cloud Launcher, and Deployment Manager. However, this is not essential.
When you sit the GCP exam, you may find yourself being asked to enable Kubernetes monitoring or logging. In this brief demonstration, I'm going to show you how to enable Stackdriver logging and monitoring for an existing Kubernetes cluster.
To do this, let's browse to the Clusters page under Kubernetes Engine. From here, I can click the Edit icon to edit my cluster. Now, to enable both logging and monitoring, I just have to choose Enable from the Stackdriver Kubernetes Engine Monitoring dropdown. So if I scroll down here, we can see it right here, so we'll go ahead and enable this.
Now you might notice right here, there are also two other options. These Legacy options for monitoring and logging are also supported. However, Stackdriver Kubernetes Engine Monitoring is the preferred option, beginning with GKE versions 1.12.7 and 1.13, while Legacy Stackdriver is the default option up through GKE version 1.13.
Because these Legacy options aren't getting any future improvements, nor do they offer features that are present in Stackdriver Kubernetes Engine Monitoring, you should use the Stackdriver Kubernetes Engine Monitoring whenever possible. We'll go ahead and set this back to enabled again, and you'll see here that when I enable the Stackdriver Kubernetes Engine Monitoring, I can't use the Legacy options, and that's because they're not compatible.
So having said that, I'm going to click Save down here at the bottom, to enable monitoring and logging for my cluster. And we can see here our Stackdriver Kubernetes Engine Monitoring is now enabled, and our Legacy are disabled, so that's pretty much it. We now have Stackdriver logging and monitoring enabled for our existing Kubernetes cluster.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.