What is Google Cloud Platform?

Google Cloud Platform (GCP) is a comprehensive suite of cloud services provided by Google that enables organizations and developers to build, deploy, and operate applications and infrastructure at scale on Google’s global infrastructure. Launched in 2008, GCP is designed to provide scalable, secure, and flexible cloud computing resources that leverage Google’s own cutting-edge technology and infrastructure — the same platform that powers Google’s core products like Search, Gmail, YouTube, and more.

At its core, GCP offers Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) solutions. These include virtual machines, container orchestration, serverless computing, managed databases, data analytics, AI and machine learning, networking, security, developer tools, and hybrid cloud solutions. It supports open standards and integrates with popular tools and frameworks, making it developer-friendly and adaptable to a variety of business needs.

GCP stands out for its emphasis on advanced data analytics, machine learning capabilities, and a global network backbone, providing low latency and high throughput for users worldwide.

Major Use Cases of Google Cloud Platform

GCP’s extensive service offerings enable a diverse set of applications and business models. Some of the primary use cases include:

1. Cloud-Native Application Development and Hosting

Developers can build and deploy scalable web and mobile applications using Google Compute Engine (VMs), Google Kubernetes Engine (GKE) for container orchestration, App Engine for serverless PaaS, and Cloud Run for fully managed serverless containers. GCP’s auto-scaling and global load balancing capabilities ensure apps remain highly available and responsive under varying loads.

2. Big Data Analytics and Data Warehousing

Google BigQuery is a fully managed, serverless data warehouse that allows organizations to analyze petabytes of data quickly using SQL-like queries without worrying about infrastructure management. Integration with Dataflow (stream and batch processing) and Dataproc (managed Hadoop/Spark) enables real-time analytics pipelines and big data workflows, supporting data-driven decision-making and business intelligence.

3. Machine Learning and AI Solutions

GCP provides a rich set of AI and ML tools including Vertex AI for building, deploying, and managing ML models, AutoML for no-code model training, and APIs for vision, speech, translation, and natural language understanding. These tools enable enterprises to embed intelligence into their applications, automate workflows, and enhance user experiences.

4. Hybrid and Multi-Cloud Deployments

With Anthos, GCP offers a platform for managing containerized workloads across on-premises, Google Cloud, and other cloud providers, enabling consistent security, policy enforcement, and workload portability in multi-cloud environments.

5. Data Storage and Backup

From object storage with Cloud Storage to relational databases with Cloud SQL and Cloud Spanner (a globally distributed, strongly consistent database), GCP provides options tailored to various performance and scalability needs. Cloud Storage supports multi-tiered storage classes for cost optimization, including Nearline, Coldline, and Archive.

6. Internet of Things (IoT) and Edge Computing

Cloud IoT Core allows secure connection and management of IoT devices, streaming data into GCP for processing and analytics. Combined with Edge TPU, GCP enables ML inferencing at the edge, critical for latency-sensitive applications.

7. Enterprise Collaboration and Productivity

Integration with Google Workspace (formerly G Suite) offers organizations cloud-native collaboration tools such as Gmail, Drive, Docs, Sheets, and Meet, boosting productivity and teamwork.

How Google Cloud Platform Works Along with Architecture

Global Infrastructure and Resource Organization

GCP’s foundation is its global infrastructure consisting of:

• Regions: Geographically distinct locations with multiple zones, providing geographic redundancy and proximity to users.
• Zones: Isolated data centers within a region designed to reduce failure impact and enable high availability.
• Network Backbone: Google owns one of the world’s largest and most advanced private fiber optic networks, enabling high-speed, low-latency, and secure data transfers across regions and zones.

Resource Abstraction and Service Layers

GCP organizes its services across multiple layers:

• Compute Layer:
  Includes virtual machines (Compute Engine), managed Kubernetes clusters (GKE), serverless platforms (Cloud Functions, Cloud Run), and App Engine for fully managed PaaS applications. This layer abstracts away infrastructure management, enabling developers to focus on code.
• Storage Layer:
  Cloud Storage offers object storage, Persistent Disks provide block storage for Compute Engine instances, Filestore provides managed NFS file storage, and managed database services include Cloud SQL (relational), Cloud Spanner (globally distributed), Firestore (NoSQL document database), and Bigtable (wide-column store).
• Data and Analytics Layer:
  BigQuery enables serverless data warehousing and analytics, Dataflow handles stream and batch data processing, Dataproc offers managed Hadoop and Spark clusters, and Pub/Sub facilitates messaging and event ingestion.
• AI and Machine Learning Layer:
  Provides tools for model training, deployment, and pre-trained APIs.
• Networking Layer:
  Virtual Private Cloud (VPC) provides isolated networks, Cloud Load Balancing distributes traffic globally, Cloud CDN accelerates content delivery, and Cloud Interconnect offers private connectivity options.
• Security Layer:
  Encompasses Identity and Access Management (IAM), Cloud Security Command Center for threat detection, encryption by default, and compliance certifications.

Service-Oriented Architecture

GCP services are accessible via RESTful APIs, SDKs, and CLIs. They are designed to be composable, enabling developers to create complex workflows by integrating multiple services seamlessly.

Basic Workflow of Google Cloud Platform

1. Project Setup:
   Everything in GCP is organized under projects, which act as containers for resources, billing, and permissions. Start by creating a new project.
2. Enable APIs:
   Activate the APIs needed for your project (e.g., Compute Engine API, BigQuery API).
3. Provision Resources:
   Using the Console, Cloud SDK (gcloud), or Infrastructure as Code (Terraform), provision compute instances, storage buckets, databases, or clusters.
4. Develop and Deploy Applications:
   Deploy your application code using App Engine, Cloud Run, or Kubernetes Engine. Serverless options eliminate infrastructure management.
5. Ingest and Process Data:
   Use Pub/Sub for real-time data ingestion, Dataflow for processing, and BigQuery for querying and analytics.
6. Monitor and Maintain:
   Configure Cloud Monitoring dashboards and alerts to track performance and health. Use Cloud Logging to troubleshoot.
7. Scale and Optimize:
   Take advantage of auto-scaling features, set budgets and quotas, and leverage cost management tools to optimize cloud spend.
8. Secure Your Resources:
   Define IAM roles and policies, enable encryption, and regularly audit access and security configurations.

Step-by-Step Getting Started Guide for Google Cloud Platform

Step 1: Create a Google Cloud Account

Go to https://cloud.google.com, sign up, and complete account verification. New users receive $300 free credits valid for 90 days.

Step 2: Set Up a New Project

In the Google Cloud Console, create a new project. Assign it a meaningful name and link it to your billing account.

Step 3: Install and Configure Google Cloud SDK

Download the Google Cloud SDK from https://cloud.google.com/sdk, install it on your local machine, and authenticate with:

gcloud auth login
gcloud config set project [PROJECT_ID]

Step 4: Enable Necessary APIs

Enable APIs relevant to your use case (e.g., Compute Engine, Cloud Storage) through the Console or CLI:

gcloud services enable compute.googleapis.com

Step 5: Provision Resources

Create compute instances or Kubernetes clusters via Console or CLI, for example:

gcloud compute instances create my-instance --zone=us-central1-a

Step 6: Deploy Your Application

For App Engine:

gcloud app deploy

For Kubernetes Engine, build and push your container image, then deploy with kubectl.

Step 7: Set Up Storage and Databases

Create Cloud Storage buckets, set access policies, and upload objects:

gsutil mb gs://my-bucket
gsutil cp localfile.txt gs://my-bucket/

Create and connect to managed databases like Cloud SQL.

Step 8: Monitor and Optimize

Use Cloud Monitoring and Logging for operational visibility. Review billing reports and set budgets.

The post Google Cloud Platform (GCP): An In-Depth Guide to Architecture, Use Cases, and Getting Started appeared first on scmGalaxy.

How to setup Kubernetes Dashboard in EKS using NodePort?

Step 1: Deploy the Dashboard
# Deploy the Kubernetes dashboard to your cluster:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml

# Deploy heapster to enable container cluster monitoring and performance analysis on your cluster:

$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/heapster.yaml

# Deploy the influxdb backend for heapster to your cluster:

$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/influxdb.yaml

# Create the heapster cluster role binding for the dashboard:

$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/rbac/heapster-rbac.yaml

Step 2: Create an eks-admin Service Account and Cluster Role Binding
# Create a file called eks-admin-service-account.yaml with the text below:

vi eks-admin-service-account.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: eks-admin
  namespace: kube-system

$ kubectl apply -f eks-admin-service-account.yaml

vi eks-admin-cluster-role-binding.yaml

apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: eks-admin
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: eks-admin
  namespace: kube-system

$ kubectl apply -f eks-admin-cluster-role-binding.yaml

Step 3: Retrieve an authentication token 
Retrieve an authentication token for the eks-admin service account. Copy the <authentication_token> value from the output. You use this token to connect to the dashboard.

kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep eks-admin | awk '{print $1}')

Step 4: Connect to the Dashboard Via Node Port
Retrieve an authentication token for the eks-admin service account. Copy the <authentication_token> value from the output. You use this token to connect to the dashboard.

$ kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep eks-admin | awk '{print $1}')
$ kubectl get pods --all-namespaces
$ kubectl get pods --namespace=kube-system
$ kubectl get svc --all-namespaces

$ kubectl edit svc/kubernetes-dashboard --namespace=kube-system
or
$ kubectl -n kube-system edit service kubernetes-dashboard
Just change "type: NodePort" only

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: 2018-07-27T10:22:50Z
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
  resourceVersion: "3288196"
  selfLink: /api/v1/namespaces/kube-system/services/kubernetes-dashboard
  uid: 03f2f747-9187-11e8-9432-02b761c0deac
spec:
  clusterIP: 10.100.194.75
  externalTrafficPolicy: Cluster
  ports:
  - nodePort: 30530
    port: 443
    protocol: TCP
    targetPort: 8443
  selector:
    k8s-app: kubernetes-dashboard
  sessionAffinity: None
  type: NodePort
status:
  loadBalancer: {}

$ kubectl describe pods kubernetes-dashboard-7d5dcdb6d9-mt9b9 --namespace=kube-system 
#Find which node is running and get a Port of SVC

$ kubectl get svc --all-namespaces
$ kubectl get pods --all-namespaces
$ kubectl describe pods kubernetes-dashboard-7d5dcdb6d9-h9dcb --namespace=kube-system

Step 5: Connect to the Dashboard Via ClustorIP and Proxy
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

https://10.16.39.28:30178/

IMPORTANT – Kubernetes Dashboard should be HTTPS

The post How to setup Kubernetes Dashboard in EKS using NodePort? appeared first on scmGalaxy.

What is Annotations in Kubernetes?

There are two way using you can attach metadata to Kubernetes objects.

1. labels
2. annotations

Kubernetes annotations is used to attach arbitrary non-identifying metadata to objects. Clients such as tools and libraries can retrieve this metadata.

In contrast, annotations are not used to identify and select objects. The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels.

Annotations, like labels, are key/value maps:

apiVersion: extensions/v1beta1

kind: Deployment

metadata:

  annotations:

    kompose.cmd: ./kompose convert

    kompose.version: “”

FORMAT

"metadata": {</p>
<p class="p1"><span class="Apple-converted-space">  </span>"annotations": {</p>
<p class="p1"><span class="Apple-converted-space">    </span>"key1" : "value1",</p>
<p class="p1"><span class="Apple-converted-space">    </span>"key2" : "value2"</p>
<p class="p1"><span class="Apple-converted-space">  </span>}</p>
<p class="p1">}</p>

Here are some examples of information that could be recorded in annotations:

1. Build, release, or image information like timestamps, release IDs, git branch, PR numbers, image hashes, and registry address.
2. Pointers to logging, monitoring, analytics, or audit repositories.

More

https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/

The post What is Annotations in Kubernetes? appeared first on scmGalaxy.

In simple line, Amazon EKS is generally available, bringing fully-managed Kubernetes to AWS.

Amazon launched Amazon EKS in November at its re:Invent 2017 conference. Till the time this article is written, Amazon EKS is available in the US East (N. Virginia) and US West (Oregon) Regions only.

The cost of running EKS is $0.20 per hour for the EKS Control Plane, apart from EC2, EBS, and Load Balancing prices for resources that run in your account.

How does Amazon EKS work?

Amazon EKS works by provisioning (starting) and managing the Kubernetes control plane for you. At a high level, Kubernetes consists of two major components – a cluster of ‘worker nodes’ that run your containers and the control plane that manages when and where containers are started on your cluster and monitors their status.

Without Amazon EKS, you have to run both the Kubernetes control plane and the cluster of worker nodes yourself. With Amazon EKS, you provision your cluster of worker nodes using the provided Amazon Machine Image (AMI) and AWS CloudFormation script and AWS handles provisioning, scaling, and managing the Kubernetes control plane in a highly available and secure configuration. This removes a significant operational burden for running Kubernetes and allows you to focus on building your application instead of managing AWS infrastructure.

Major Features of Amazon Elastic Container Service for Kubernetes (EKS)
Amazon Elastic Container Service for Kubernetes (EKS) is a managed Kubernetes service that makes it easy for you to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane.

1. Availability and Scalability of Nodes – Amazon EKS automatically manages the availability and scalability of the Kubernetes control plane nodes that are responsible for
   1. Starting and stopping containers,
   2. Scheduling containers on virtual machines,
   3. Storing cluster data, and other tasks.
2. Health check of Nodes – Amazon EKS Automatically detects and replaces unhealthy control plane nodes for each cluster.
3. Amazon EKS Integration – Great Integration with AWS networking and security services, such as Application Load Balancers for load distribution, IAM for role based access control, and VPC for pod networking.
4. Managed Kubernetes Control Plane – Amazon EKS provides a scalable and highly-available control plane that runs across multiple AWS availability zones.
5. Kubernetes Masters in three Availability Zones – Amazon EKS runs the Kubernetes control plane across three Availability Zones in order to ensure high availability, and it automatically detects and replaces unhealthy masters.
6. Amazon EKS with IAM Authentication – Amazon EKS integrates Kubernetes RBAC (the native role based access control system for Kubernetes) with IAM authentication through a collaboration with Heptio. You can assign RBAC roles directly to each IAM entity allowing you to granularly control access permissions to your Kubernetes masters.
7. Amazon EKS with VPC Support
   Your EKS clusters run in an Amazon VPC, allowing you to use your own VPC security groups and network ACLs. No compute resources are shared with other customers. This provides you a high level of isolation and helps you use Amazon EKS to build highly secure and reliable applications.
8. Container Interface – EKS uses the Amazon VPC CNI to allow Kubernetes pods to receive IP addresses from the VPC means The Container Network Interface for Kubernetes uses Elastic Network Interfaces to provide secondary IP addresses for Kubernetes Pods.
9. Amazon EKS Logging
   Amazon EKS is integrated with AWS CloudTrail to provide visibility and audit history of your cluster and user activity. You can use CloudTrail to view API calls to the Amazon EKS API.
10. Amazon EKS with EBS – Kubernetes PersistentVolumes (used for cluster storage) are implemented as Amazon Elastic Block Store (EBS) volumes.
11. Amazon EKS with Route 53 – The External DNS project allows services in Kubernetes clusters to be accessed via Route 53 DNS records. This simplifies service discovery and supports load balancing.
12. Amazon EKS Support – Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all the existing plugins and tooling from the Kubernetes community.

Reference
EKS Getting Started Guide –
EKS Publication
EKS FAQ

The post What is EKS and How EKS can help you? appeared first on scmGalaxy.

Kubernetes at Public Cloud

1. Google Container Engine – Google Kubernetes Engine is a powerful cluster manager and orchestration system for running your Docker containers.
2. ECS – Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service that makes it easy to run, stop, and manage Docker containers on a cluster.
3. EKS – Amazon Elastic Container Service for Kubernetes (Amazon EKS) makes it easy to deploy, manage, and scale containerized applications using Kubernetes on AWS.

Kubernetes cli tools

1. kubectl – Main CLI tool for running commands and managing Kubernetes clusters.
2. JSONPath – Syntax guide for using JSONPath expressions with kubectl.
3. kubeadm – CLI tool to easily provision a secure Kubernetes cluster.
4. kubefed – CLI tool to help you administrate your federated clusters.
5. Minikube – This is the simplest way to get a Kubernetes cluster on your Mac or Windows machine.
6. Kops – kops helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters from the command line. AWS (Amazon Web Services) is currently officially supported, with GCE in beta support , and VMware vSphere in alpha, and other platforms planned.

kubernetes config reference

1. kubelet – The primary node agent that runs on each node. The kubelet takes a set of PodSpecs and ensures that the described containers are running and healthy.
2. Container runtime – Container runtime is Docker engine which resides in each node
3. kube-proxy – Can do simple TCP/UDP stream forwarding or round-robin TCP/UDP forwarding across a set of back-ends.

Cluster control plane (AKA master)

1. kube-apiserver – REST API that validates and configures data for API objects such as pods, services, replication controllers.
2. Cluster state store – All persistent cluster state is stored in an instance of etcd. This provides a way to store configuration data reliably.
3. kube-controller-manager – Daemon that embeds the core control loops shipped with Kubernetes.
4. kube-scheduler – Scheduler that manages availability, performance, and capacity.
5. Federation – A single Kubernetes cluster may span multiple availability zones.
6. federation-apiserver – API server for federated clusters.
7. federation-controller-manager – Daemon that embeds the core control loops shipped with Kubernetes federation

Kubernetes Add ons

1. DNS
2. Ingress controller
3. Heapster (resource monitoring)
4. Dashboard (GUI)

The post Understanding the tools sets in kubernetes ecosystem appeared first on scmGalaxy.

Error 1 – Error starting host:  Error getting state for host: machine does not exist

<p style="font-weight: 400;">D:\kubernete>minikube-windows-amd64.exe start --kubernetes-version="v1.8.0" --vm</p>
<p style="font-weight: 400;">-driver="virtualbox" --alsologtostderr</p>
<p style="font-weight: 400;">W0110 <span data-term="goog_1571914274">12:16:04.517163</span>   10504 root.go:148] Error reading config file at C:\Users</p>
<p style="font-weight: 400;">\panan4\.minikube\config\config.json: open C:\Users\panan4\.minikube\config\conf</p>
<p style="font-weight: 400;">ig.json: The system cannot find the file specified.</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914275">12:16:04.528163</span>   10504 notify.go:109] Checking for updates...</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914276">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/k8s-minikube/storage-provisioner:v1.8.0" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/k8s-minikube/storage-provisioner:v1.8.0&source=gmail&ust=1515821717506000&usg=AFQjCNHilUJGRCqAxx0Naa3yTEDGQ9X2Dw">r.io/k8s-minikube/storage-provisioner:v1.8.0</a> at C:\Users\panan4\.minikube\cache\</p>
<p style="font-weight: 400;">images\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717506000&usg=AFQjCNHwyTmXfOb8jcAGQbTDyIr_DuEirg">gcr.io</a>\k8s-minikube\storage-provisioner_v1.8.0</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914277">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5&source=gmail&ust=1515821717506000&usg=AFQjCNFAVT9yppX_1usJ2E0YbShOwXUE9A">r.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5</a> at C:\Users\panan4\.mi</p>
<p style="font-weight: 400;">nikube\cache\images\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717507000&usg=AFQjCNF--H_EnOHq-1gORX9rvCyL0guvAA">gcr.io</a>\google_containers\k8s-dns-dnsmasq-nanny-amd64_1.14.5</p>
<p style="font-weight: 400;">Starting local Kubernetes v1.8.0 cluster...</p>
<p style="font-weight: 400;">Starting VM...</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914278">12:16:05.901354</span>   10504 cluster.go:74] Skipping create...Using existing ma</p>
<p style="font-weight: 400;">chine configuration</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914279">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/google_containers/kubernetes-dashboard-amd64:v1.6.3" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/google_containers/kubernetes-dashboard-amd64:v1.6.3&source=gmail&ust=1515821717507000&usg=AFQjCNERLC4qpuUBrUqm5OvSjac96pWNKw">r.io/google_containers/kubernetes-dashboard-amd64:v1.6.3</a> at C:\Users\panan4\.min</p>
<p style="font-weight: 400;">ikube\cache\images\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717507000&usg=AFQjCNF--H_EnOHq-1gORX9rvCyL0guvAA">gcr.io</a>\google_containers\kubernetes-dashboard-amd64_v1.6.3</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914280">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5&source=gmail&ust=1515821717507000&usg=AFQjCNFhurp_V-c-NFhO73j_Zjakc4fptw">r.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5</a> at C:\Users\panan4\.minikub</p>
<p style="font-weight: 400;">e\cache\images\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717507000&usg=AFQjCNF--H_EnOHq-1gORX9rvCyL0guvAA">gcr.io</a>\google_containers\k8s-dns-kube-dns-amd64_1.14.5</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914281">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/google-containers/kube-addon-manager:v6.4-beta.2" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/google-containers/kube-addon-manager:v6.4-beta.2&source=gmail&ust=1515821717507000&usg=AFQjCNEFsklfJPJCpLyEX7qsaLsvUDDRow">r.io/google-containers/kube-addon-manager:v6.4-beta.2</a> at C:\Users\panan4\.miniku</p>
<p style="font-weight: 400;">be\cache\images\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717507000&usg=AFQjCNF--H_EnOHq-1gORX9rvCyL0guvAA">gcr.io</a>\google-containers\kube-addon-manager_v6.4-beta.2</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914282">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/google_containers/k8s-dns-sidecar-amd64:1.14.5" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/google_containers/k8s-dns-sidecar-amd64:1.14.5&source=gmail&ust=1515821717507000&usg=AFQjCNEOfewUFCow70i9iSK2lBFDahW47A">r.io/google_containers/k8s-dns-sidecar-amd64:1.14.5</a> at C:\Users\panan4\.minikube</p>
<p style="font-weight: 400;">\cache\images\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717507000&usg=AFQjCNF--H_EnOHq-1gORX9rvCyL0guvAA">gcr.io</a>\google_containers\k8s-dns-sidecar-amd64_1.14.5</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914283">12:16:05.901354</span>   10504 cache_images.go:290] Attempting to cache image: gc</p>
<p style="font-weight: 400;"><a href="http://r.io/google_containers/pause-amd64:3.0" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://r.io/google_containers/pause-amd64:3.0&source=gmail&ust=1515821717507000&usg=AFQjCNF2E15ZIwSbjHDnD4zxOcapo39PIQ">r.io/google_containers/pause-amd64:3.0</a> at C:\Users\panan4\.minikube\cache\images</p>
<p style="font-weight: 400;">\<a href="http://gcr.io/" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://gcr.io&source=gmail&ust=1515821717507000&usg=AFQjCNF--H_EnOHq-1gORX9rvCyL0guvAA">gcr.io</a>\google_containers\pause-amd64_3.0</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914284">12:16:05.911354</span>   10504 cache_images.go:78] Successfully cached all images</p>
<p style="font-weight: 400;">.</p>
<p style="font-weight: 400;">I0110 <span data-term="goog_1571914285">12:16:06.292552</span>   10504 cluster.go:83] Machine state:  Error</p>
<p style="font-weight: 400;">E0110 <span data-term="goog_1571914286">12:16:06.292552</span>   10504 start.go:150] Error starting host: Error getting s</p>
<p style="font-weight: 400;">tate for host: machine does not exist.</p>
<p style="font-weight: 400;"></p>
<p style="font-weight: 400;">Retrying.</p>
<p style="font-weight: 400;">E0110 <span data-term="goog_1571914287">12:16:06.292552</span>   10504 start.go:156] Error starting host:  Error getting</p>
<p style="font-weight: 400;">state for host: machine does not exist</p>
<p style="font-weight: 400;">================================================================================</p>
<p style="font-weight: 400;"></p>
<p style="font-weight: 400;">An error has occurred. Would you like to opt in to sending anonymized crash</p>
<p style="font-weight: 400;">information to minikube to help prevent future errors?</p>
<p style="font-weight: 400;">To opt out of these messages, run the command:</p>
<p style="font-weight: 400;">        minikube config set WantReportErrorPrompt false</p>
<p style="font-weight: 400;">================================================================================</p>

Solutions

Please use/install minikube in the c drive.

The post Kubernetes minikube errors and Solutions appeared first on scmGalaxy.