prgcont/workshop-k8s

k8s related workshops

workshop-k8s's Issues

lesson 1 - persistent volume exercise does not currently work on DO setup

Add note to persistent volume exercise to use selector in hello Deployment to deploy pods on single node only, so that content of PV is same in each pod.

RBAC for shared envs

If we go to support workshop on shared envs, we should enable RBAC and limit people to their namespaces

explore infrastructure sponsorship for cloud provider

What do we need?

• cloud infra capable of running k8s and ideally with some native ingressing.

What can we offer? (open for discussion - where do we draw the line)

• logo on slides,
• thanks in beginning?
• other

several options are:

• concur ?
• if someone can think of something, please comment.

Find easy way to setup k8s cluster on cloud provider VM

Choose and implement one of following options:

• managed kuberentes (azure, aws, gcp)
  • do we have all privileges for cluster (rbac, etc)
• install k8s on cloud provider

replace echo by export

Now we can select one pod and execute:

$ echo POD_NAME=$(kubectl get pods | grep hello | cut -f 1 -d ' ' | head -n 1)
$ kubectl exec -ti $POD_NAME touch /srv/test_file

-> export POD_NAME

Istio 101

The goal is to show Istio basic use cases and demonstrate basic functionality.

We will be using shared beefy Kubernetes cluster for all attendees. Plan is show them basics and then let them play with Istio and try bookinfo-like application.

Items to cover:

• How istio works
  • reuse image from https://medium.com/vescloud/battle-testing-istio-1-0-a0248ce68403
  • Sidecar, pilot, mixer, citadel
• How Istio was installed kubectl apply -f istio-demo.yml
• Kiali monitoring
• Istio routing vs Kubernetes ingress resource
• Basic resources: Gateway, VirtualService, DestinationRule, ServiceEntry and relations between them

@dbecvarik @pupapaik please add any ideas

Troubleshooting playground

Prepare broken deployment to demonstrate troubleshooting options:

• 0 replicas
• wrong service selector
• typo in container image
• missing label on node (nodeSelector)
• too many resources requested (wrong unit)

Add solution to repo but in crypted form.

Check that lesson-1 works with External env

Re-check the whole workshop

We need to re-check the whole workshop to make sure that everything works smoothly on the last version of minikube.

• lesson 1
• lesson 2

namespaces

Every sample should be run in personalized namespace - export variable?
Is there an equivalent of oc project switching in kubectl?