Kubernetes doesn’t have to be that way, you can use this simple cheat sheet to understand the basics. Kubernetes Architecture Components Master Node : The control plane of the cluster, responsible for managing the state of the cluster, scheduling and managing workloads, and providing a centralized configuration. Worker Nodes : These are the machines (physical or virtual) that run your applications and services. Pods are scheduled on worker nodes, and the containers within those pods run on the worker nodes. etcd : A distributed key-value store that provides a source of truth for the cluster state and configuration. The master node communicates with etcd to ensure the desired state of the cluster is maintained. API Server : The front-end of the master node, responsible for serving the RESTful API used by all other components to interact with the cluster. Controller Manager : Monitors the state of the cluster and makes changes as necessary to ensure the desired state is maintained. Sched...
A new multi-platform CloudWatch agent is available. You can use a single agent to collect both system metrics and log files from Amazon EC2 instances and on-premises servers. The new agent supports both Windows Server and Linux and enables you to select the metrics to be collected, including sub-resource metrics such as per-CPU core. We recommend you use the new agent instead of the older monitoring scripts to collect metrics and logs. For more information about the CloudWatch agent, see Collect Metrics from Amazon EC2 Instances and On-Premises Servers with the CloudWatch Agent in the Amazon CloudWatch User Guide Package Contents The package for the monitoring scripts contains the following files: CloudWatchClient.pm – Shared Perl module that simplifies calling Amazon CloudWatch from other scripts. mon-put-instance-data.pl – Collects system metrics on an Amazon EC2 instance (memory, swap, disk space utilization) and sends them t...