udacity / ud615

Course code for Scalable Microservices with Kubernetes

UD615: Scalable Microservices with Kubernetes

This is the code for Scalable Microservices with Kubernetes. In this course 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

Course Description

Kubernetes is all about applications and in this course 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 an example 12 Factor application that we'll be using throughout the course. During this course you will be working with the following Docker images:

• udacity/example-monolith - Monolith includes auth and hello services.
• udacity/example-auth - Auth microservice. Generates JWT tokens for authenticated users.
• udacity/example-hello - Hello microservice. Greets authenticated users.
• nginx - Frontend to the auth and hello services.

Links

• Kubernetes
• gcloud Tool Guide
• Docker
• etcd
• nginx

ud615's Issues

Missing key in healthy-monolith.yaml ?

According to video MHC in file kubernetes/pods/healthy-monolith.yaml at group spec/containers/readinessProbe there should be a key periodSeconds with value 10.

It does not exist.

Either the video or the file must be amended.

The Kubernetes Probe API suggests that the video is correct and the file is missing the key.
The key should probably be inserted at line 34 to conform with order of group livenessProbe above.

Anti-pattern: No security context for pods

Dear Colleague,

We are looking to find ways to help developers find security misconfigurations, i.e., violation of security best practices in Kubernetes manifests. We have noticed an instance of no security context in one of your Kubernetes manifests. The recommended practice is use of security context for pods. Without defining a security context for the pod, a container may run with root privilege and write permission into the root file system, making the Kubernetes cluster vulnerable. For examples of Kubernetes security anti-patterns we are following our peer-reviewed publication on Kubernetes security best practices (https://arxiv.org/pdf/2006.15275.pdf).

Location:

ud615/kubernetes/pods/secure-monolith.yaml

Line 9 in ff0bf7e

- name: nginx

Please use securityContext to fix this misconfiguration. We would like to hear if you agree to fix this misconfiguration or have fixed the misconfiguration.

This example is not working anymore

This example is too old, it cant' work.

Certificate is expired

openssl x509 -enddate -noout -in kubernetes/tls/cert.pem
notAfter=Apr 26 04:09:08 2017 GMT

Misleading app/README.md

$./server
2016/04/15 06:34:12 Starting server...
2016/04/15 06:34:12 HTTP service listening on 0.0.0.0:5000
2016/04/15 06:34:12 Health service listening on 0.0.0.0:5001
2016/04/15 06:34:12 Started successfully.

Default ports for HTTP and Health services are 80 and 81 respectively.

Issue with circular dependencies

In Lesson 2 part 11 "Create an Image" I get the following error and am unable to proceed:

`cloudshell:~/go/src/github.com/udacity/ud615/app/monolith (udacity-230007)$ go get -u

import cycle not allowed
package github.com/udacity/ud615/app/monolith
imports flag
imports errors
imports runtime
imports internal/cpu
imports runtime`

Any idea how to proceed?

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

When I use kubectl version v1.17.2 to create the auth deployment:

kubectl create -f deployments/auth.yaml

Then I get the error:

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

Rolling Updates section needs a exampe-auth:2.0.0 tag

In the deploying Microservices section of the class under Rolling Updates. Kelsey does a rolling update by editing demployments/auth.yml. In the video he changes the image to kelseyhightower/auth:2.0.0.

Following along using this cloned app deployments/auth.yml has udacity/example-auth:1.0.0.
https://github.com/udacity/ud615/blob/master/kubernetes/deployments/auth.yaml#L15

However you do not have a tagged version udacity/example-auth:2.0.0 in your Docker Hub repo. This will cause the rolling update to fail.
https://hub.docker.com/r/udacity/example-auth/tags/

I need to use Kelsey's auth:2.0.0 image to complete the process.

Enjoyed the class. Thanks!