googlecodelabs / orchestrate-with-kubernetes Goto Github PK

View Code? Open in Web Editor NEW

503.0 28.0 311.0 109 KB

Orchestrating the Cloud with Kubernetes

Home Page: https://codelabs.developers.google.com/codelabs/cloud-orchestrate-with-kubernetes/

License: Apache License 2.0

Shell 100.00%

orchestrate-with-kubernetes's Introduction

Orchestrating the Cloud with Kuberenetes

In this Codelab you will learn how to:

Provision a complete Kubernetes using Google Container Engine
Deploy and manage Docker containers using kubectl

Kubernetes Version: 1.2.2

Setup GCE and Enable Cloud Shell

In this section you will create a Google Compute Engine (GCE) account. GCE will allow you to the create VMs, Networks, and Storage volumes required for this workshop. GCE also provides the Cloud Shell computing environment that will be used complete the labs.

Labs

Clone this Repository

git clone https://github.com/googlecodelabs/orchestrate-with-kubernetes.git

Provision Kubernetes using GKE

Kubernetes is a distributed system composed of a collection of microservices. Like any system Kubernetes must be installed and configured. In this section you will install Kubernetes from the ground up with the minimal configuration required to get a cluster up and running.

Kubernetes can be configured with many options and add-ons, but can be time consuming to bootstrap from the ground up. In this section you will bootstrap Kubernetes using Google Container Engine (GKE).

Provision a Kubernetes Cluster with GKE

Managing Applications with Kubernetes

Kubernetes is all about applications and in this section you will utilize the Kubernetes API to deploy, manage, and upgrade applications. In this part of the workshop you will use an example application called "app" to complete the labs.

App is hosted on GitHub and provides an example 12 Facter application. During this workshop you will be working with the following Docker images:

kelseyhightower/monolith - Monolith includes auth and hello services.
kelseyhightower/auth - Auth microservice. Generates JWT tokens for authenticated users.
kelseyhightower/hello - Hello microservice. Greets authenticated users.
ngnix - Frontend to the auth and hello services.

Labs

For each of the following labs, you should be in the kubernetes dir:

cd orchestrate-with-kubernetes/kubernetes

orchestrate-with-kubernetes's People

Contributors

Stargazers

Watchers

Forkers

ianlewis arturgaleno pvasconcellos-daitan naheedmk roneda wilsonmar weburnit freedev mbrioski nkumar15 lflinks direkshan-digital jmyung prabeesh cristobal-vl sanketjpatel jhaals stevepetcu sylvanasbeta bttrung adityap101 vignesh97 a-r-chandra anandcpm goungoun tanzhongyi003 miguelfrancisco85 ymaghzaz leewalter suvink nowjean pariyat seshsankar kalaiprakashgit plusx2012 agasthik bhanditz pradhyu aorinevo lovie kustode anxious-coder-lhs dannyarw dmitryrendov prajesh-ananthan injeti-manohar crazyzia bguruprasad entrpn laurauzcategui k8expert shillpi isdzulqor kamalhunzai rd1981 mtpradoc henrypan githubgk naushad-rahman sevaroy kubernetes-tn alopsing sangam14 dabansal ibrahim00017 9643826476 pankajps danilodesousacubas arkdabk anilkumarkoduri chengyh2golang yonghochoi marsyang1 aadice02 gatsby-lee syalanuj balasambamurhty aismailov latermonk matheustp hardik-id babudasthagir mr-talukdar saravanastar cssheth1711 agatagruza rch1991 barbietunnie winbugsmx varunraj05 mrmicjam prakashk0301 sagar4422 jirokakai shajug nishant8bits cloudtwter patechoc dhirajhargode mqsrinc

orchestrate-with-kubernetes's Issues

It is causing Error In qwiklabs

error: unable to recognize "deployments/frontend.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

Error: unable to recognize "deployments/auth.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

I am doing this lab in Qwiklabs - Managing Deployments Using Kubernetes Engine
When I use command kubectl create -f deployments/auth.yaml after changing image in auth.yaml to kelseyhightower/auth:1.0.0
I am facing this error. I had lost enough credits because of this. Please fix it asap.

Error While Deployment of auth and hello apps

Errors:
"""
Error from server (BadRequest): error when creating "deployments/auth.yaml": Deployment in version "v1" cannot be handled as a Deployment: v1.Deployment.Spec: v1.DeploymentSpec.Selector: v1.LabelSelector.MatchLabels: ReadMapCB: expect { or n, but found ", error found in #10 byte of ...|hLabels":"app:auth"}|..., bigger context ...|},"spec":{"replicas":1,"selector":{"matchLabels":"app:auth"},"template":{"metadata":{"labels":{"app"|...
"""

"""
error: error validating "deployments/auth.yaml": error validating data: ValidationError(Deployment.spec.selector.matchLabels): invalid type for io.k8s.apimac
hinery.pkg.apis.meta.v1.LabelSelector.matchLabels: got "string", expected "map"; if you choose to ignore these errors, turn validation off with --validate=fa
lse
"""

Error found for several files as a result of an outdated api usage

error: unable to recognize "deployments/frontend.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

This is the error which can be seen while running files like "auth.yaml"

Deployment yaml files are outdated and throw errors when using with Kubernetes v1.19.2 (Qwiklabs)

All deployment yaml files need to be updated in order to work with latest Kubernetes versions.
The apiVersion for deployment objects has changed and is now apps/v1 and also selectors are mandatory.

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: auth
spec:
  replicas: 1
  selector:
    matchLabels:      
      app: auth
      track: stable
  template:
    metadata:
      labels:
        app: auth
        track: stable
    spec:
      containers:
        - name: auth
          image: "kelseyhightower/auth:2.0.0"
          ports:
            - name: http
              containerPort: 80
            - name: health
              containerPort: 81
          resources:
            limits:
              cpu: 0.2
              memory: "10Mi"
          livenessProbe:
            httpGet:
              path: /healthz
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            periodSeconds: 15
            timeoutSeconds: 5
          readinessProbe:
            httpGet:
              path: /readiness
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            timeoutSeconds: 1
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: frontend
spec:
  replicas: 1
  selector:
    matchLabels:
      app: frontend
      track: stable
  template:
    metadata:
      labels:
        app: frontend
        track: stable
    spec:
      containers:
        - name: nginx
          image: "nginx:1.9.14"
          lifecycle:
            preStop:
              exec:
                command: ["/usr/sbin/nginx","-s","quit"]
          volumeMounts:
            - name: "nginx-frontend-conf"
              mountPath: "/etc/nginx/conf.d"
            - name: "tls-certs"
              mountPath: "/etc/tls"
      volumes:
        - name: "tls-certs"
          secret:
            secretName: "tls-certs"
        - name: "nginx-frontend-conf"
          configMap:
            name: "nginx-frontend-conf"
            items:
              - key: "frontend.conf"
                path: "frontend.conf"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-canary
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hello
      track: canary
      version: 2.0.0
  template:
    metadata:
      labels:
        app: hello
        track: canary
        version: 2.0.0
    spec:
      containers:
        - name: hello
          image: kelseyhightower/hello:2.0.0
          ports:
            - name: http
              containerPort: 80
            - name: health
              containerPort: 81
          resources:
            limits:
              cpu: 0.2
              memory: 10Mi
          livenessProbe:
            httpGet:
              path: /healthz
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            periodSeconds: 15
            timeoutSeconds: 5
          readinessProbe:
            httpGet:
              path: /readiness
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            timeoutSeconds: 1
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-green
spec:
  replicas: 3
  selector:
    matchLabels:
      app: hello
      track: stable
      version: 2.0.0
  template:
    metadata:
      labels:
        app: hello
        track: stable
        version: 2.0.0
    spec:
      containers:
        - name: hello
          image: kelseyhightower/hello:2.0.0
          ports:
            - name: http
              containerPort: 80
            - name: health
              containerPort: 81
          resources:
            limits:
              cpu: 0.2
              memory: 10Mi
          livenessProbe:
            httpGet:
              path: /healthz
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            periodSeconds: 15
            timeoutSeconds: 5
          readinessProbe:
            httpGet:
              path: /readiness
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            timeoutSeconds: 1
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello
spec:
  replicas: 3
  selector:
    matchLabels:
      app: hello
      track: stable
      version: 1.0.0
  template:
    metadata:
      labels:
        app: hello
        track: stable
        version: 1.0.0
    spec:
      containers:
        - name: hello
          image: "kelseyhightower/hello:1.0.0"
          ports:
            - name: http
              containerPort: 80
            - name: health
              containerPort: 81
          resources:
            limits:
              cpu: 0.2
              memory: "10Mi"
          livenessProbe:
            httpGet:
              path: /healthz
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            periodSeconds: 15
            timeoutSeconds: 5
          readinessProbe:
            httpGet:
              path: /readiness
              port: 81
              scheme: HTTP
            initialDelaySeconds: 5
            timeoutSeconds: 1
...

Spinnaker Deployment issue in "Deploy and Manage Cloud Environments with Google Cloud: Challenge Lab"

hello-canary.yaml

hello-canary.yaml
---This file also giving the same error-----
error: unable to recognize "deployments/hello-canary.yaml": no matches for kind "Deployment" in version "extensions/v1beta1" #14

on running the command ---> kubectl create -f deployments/hello-canary.yaml

Originally posted by @Shashwatsingh22 in #13 (comment)

error: unable to recognize "deployments/hello.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

I got this error when doing the "Creating Deployments" section of https://google.qwiklabs.com/focuses/1747?parent=catalog

It looks like this is an issue with the API version in the deployment yaml files. Doing this:

kubectl convert -f deployments/hello.yaml --output-version apps/v1 > deployments/new-hello.yaml

for each of the deployment yamls before the kubectl create -f fixed the issue for me.

kubectl run is DEPRECATED warning

I'm getting this warning during the tutorial:
kubectl run nginx --image=nginx
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl cre
ate instead.

can you please update the tutorial with the relevant changes?

api version needs to be corrected and selector line needs to be added for several yaml files

Api version needs to be corrected and selector line needs to be added for several yaml files especially here as it is creating problems while doing labs with Qwiklabs "orchestrate-with-kubernetes/kubernetes/deployments/"

error: unable to recognize "deployments/frontend.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

[ URGENT ] ; Depricated API used; Qwiklabs not working; Relevant PRs not merged;

Hi,
There are depricated API extensions/v1beta1 being used in orchestrate-with-kubernetes/kubernetes/deployments/
There are some PRs that have solved this problem but it is not merged
Please merge it a lot of people might be facing issue including me.
People are getting demotivated in qwiklabs due to this issue

Getting an error while create deployment

error: unable to recognize "deployments/auth.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

About Section Link Leads To 404

#Description:
When I click the about section link, it open a 404 page.

Image Of About Section

Link

https://codelabs.developers.google.com/codelabs/cloud-orchestrate-with-kubernetes leads to 404.

Error in Qwiklab while using this git repo

error: failed to discover supported resources: Get http://localhost:8080/apis/apps/v1beta1?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refused

googlecodelabs / orchestrate-with-kubernetes Goto Github PK

orchestrate-with-kubernetes's Introduction

Orchestrating the Cloud with Kuberenetes

Setup GCE and Enable Cloud Shell

Labs

Clone this Repository

Provision Kubernetes using GKE

Managing Applications with Kubernetes

Labs

Links

orchestrate-with-kubernetes's People

Contributors

Stargazers

Watchers

Forkers

orchestrate-with-kubernetes's Issues

Image Of About Section

Link

Recommend Projects

Recommend Topics

Recommend Org