---
# System prepended metadata

title: Kraken Day 1 and 2 09/03/2020 - 10/03/2020

---

# Kraken Day 1 and 2 09/03/2020 - 10/03/2020

## Trainers
[Rafael Tanaka](mailto:rafael.tanaka@jetstack.io)

## Setup

| Meeting ID | Password   |
| ---------- | ---------- |
| Zoom       | to confirm |

### Links

- [Download Zoom](https://zoom.us/download#client_4meeting)
- [This Doc]()
- [FlightDeck](https://flightdeck.jetstack.io) - you should receive an invitation email shortly
- [Google Cloud Shell](https://ssh.cloud.google.com/cloudshell/) - if you're redirected to the cloud editor, that can be toggled off by pressing the pencil icon in the top right

## Schedule EST timezone

| | |
|--|--|
|Start|9:00am|
|Morning break|11:00am-11:10am|
|Lunch|12:15pm-13:15pm|
|Afternoon break|15:10pm-15:20pm|
|Finish|5:30opm|

## Attendee Resources

### Overview of kubectl

https://kubernetes.io/docs/reference/kubectl/overview/

### Resources

Resource units in Kubernetes 
Meaning of CPU
Limits and requests for CPU resources are measured in cpu units. One cpu, in Kubernetes, is equivalent to 1 vCPU/Core for cloud providers and 1 hyperthread on bare-metal Intel processors.

Fractional requests are allowed. A Container with spec.containers[].resources.requests.cpu of 0.5 is guaranteed half as much CPU as one that asks for 1 CPU. The expression 0.1 is equivalent to the expression 100m, which can be read as "one hundred millicpu". Some people say "one hundred millicores", and this is understood to mean the same thing. A request with a decimal point, like 0.1, is converted to 100m by the API, and precision finer than 1m is not allowed. For this reason, the form 100m might be preferred.

CPU is always requested as an absolute quantity, never as a relative quantity; 0.1 is the same amount of CPU on a single-core, dual-core, or 48-core machine.

https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

### PV Expansion

In Kubernetes v1.11 the persistent volume expansion feature is being promoted to beta.

https://kubernetes.io/blog/2018/07/12/resizing-persistent-volumes-using-kubernetes/

## RBAC

An RBAC Role or ClusterRole contains rules that represent a set of permissions. Permissions are purely additive (there are no "deny" rules).

https://kubernetes.io/docs/reference/access-authn-authz/rbac/