The version 1.2.0-beta.0 of Kubernetes included improvements to scalability with more nodes and pods per node. It stabilized and added features from version 1.1, including the Horizontal Pod Autoscaling, Ingress, Job, DaemonSet, Deployment, ConfigMap, and Secret APIs. It also made it easier to generate resources like namespaces and secrets.

1. v1.2.0-beta.0
~ Girag

2. Outline
● released on March 7, 2016
● improved scalability
○ more nodes
○ more pods per node
● features from 1.1 time frames and stabilized
○ Horizontal pod auto-scaling API
■ add custom metrics
○ Ingress API
○ Job API
○ DaemonSet API
○ Deployment API
○ ConfigMap API
○ Make it easier to create resources
■ Namespace generation
■ Secret/config generation
■ export and convert
@girag

3. ● introduced in v1.1
● part of extensions api
● increase or decrease the pod’s count in replication controller /
deployments as per CPU utilization
● implemented as control loop
● uses heapster for metric collection (Currently CPU Utilization only)
● autoscaling and rolling-update will not work together, if rolling-update
manipulates replica count of replication controller
● will support custom metrics too
Horizontal Pod Autoscaler
@girag

4. apiVersion: extensions/v1beta1
kind: HorizontalPodAutoscaler
metadata:
name: tomcat7
namespace: default
spec:
scaleRef:
kind: ReplicationController
name: tomcat7
subresource: scale
minReplicas: 1
maxReplicas: 5
cpuUtilization:
targetPercentage: 80
Horizontal Pod Autoscaler
@girag

5. apiVersion: extensions/v1beta1
kind: HorizontalPodAutoscaler
metadata:
name: tomcat7
namespace: default
spec:
scaleRef:
kind: ReplicationController
name: tomcat7
subresource: scale
minReplicas: 1
maxReplicas: 5
cpuUtilization:
targetPercentage: 80
Horizontal Pod Autoscaler
@girag
HPA created with the name tomcat7 and act as
service with 1-5 replications depending on load
if cpuUtilization > 80** and replica < 5
spawn tomcat7
else cpuUtiliaztion fall down and sustained for 5 min
and replica > 1
remove tomcat7
** when start or stop pods the metric get noises, so
hpa wait for a while (3-5 minutes) after every action,
for picking right data.

6. ● introduced in v1.1
● part of extensions api
● set of rules that allow inbound traffic to reach the k8s cluster services.
● types
○ Single Service Ingress
○ Simple Fanout
○ Name based Virtual Hosting
○ Loadbalancing
Ingress
@girag

7. apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: virtual-hosting
spec:
rules:
- host: api.gopaddle.io
http:
paths:
- backend:
serviceName: bm-gateway
servicePort: 80
Ingress
- host: beta.gopaddle.io
http:
paths:
- backend:
serviceName: bm-dashboard
servicePort: 80
- host: doc.gopaddle.io
http:
paths:
- backend:
serviceName: bm-docs
servicePort: 80
@girag

8. Ingress
- host: beta.gopaddle.io
http:
paths:
- backend:
serviceName: bm-dashboard
servicePort: 80
- host: doc.gopaddle.io
http:
paths:
- backend:
serviceName: bm-docs
servicePort: 80
@girag
bm-
gateway
bm-
dashboard
bm-
docs
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: virtual-hosting
spec:
rules:
- host: api.gopaddle.io
http:
paths:
- backend:
serviceName: bm-gateway
servicePort: 80
172.149.22.101
api beta doc
gopaddle.io

9. ● introduced in v1.1
● part of extensions api
● build custom lifecycle of pods
● creates one or more pods and ensures that a specified number of them
successfully terminate
● control lifecycle of pods which has RestartPolicy equal to OnFailure or Never.
Jobs
@girag

10. apiVersion: extensions/v1beta1
kind: Job
metadata:
name: appsvr
spec:
completions: 4
parallelism: 2
selector:
matchLabels:
app: appsvr
template:
metadata:
name: appsvr
labels:
app: appsvr
spec:
containers:
- name: appsvr
image: bluemeric/javasvr
restartPolicy: Never
Jobs
@girag

11. apiVersion: extensions/v1beta1
kind: Job
metadata:
name: appsvr
spec:
completions: 4
parallelism: 2
selector:
matchLabels:
app: appsvr
template:
metadata:
name: appsvr
labels:
app: appsvr
spec:
containers:
- name: appsvr
image: bluemeric/javasvr
restartPolicy: Never
Jobs
@girag
Job for appsvr,
> .spec.completions : run 4 instance of appsvrs.
> .spec.parallelism : run parallelly 2 appsvrs.

12. ● introduced in v1.1
● part of extensions api
● ensures that all nodes or some (by NodeSelector) runs pod
● add a pod from Daemonset, while a node added in to k8s cluster, and
removes and clean pod when node goes off cluster.
Daemon Sets
@girag

13. apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: ds-monitor
labels:
apps: monitor
spec:
selector:
apps: monitor
template:
metadata:
name: d-monitor
labels:
apps: monitor
spec:
hostNetwork: true
containers:
- name: ds-mon
image: bm/mon:v2
Daemon Sets
@girag

14. apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: ds-monitor
labels:
apps: monitor
spec:
selector:
apps: monitor
template:
metadata:
name: d-monitor
labels:
apps: monitor
spec:
hostNetwork: true
containers:
- name: ds-mon
image: bm/mon:v2
Daemon Sets
@girag
node-01 node-02 node-03
kube-master
monitor monitor monitor
….
….
….
….
….
….
one “monitor”
pod per node

15. ● introduced in v1.1
● part of extensions api
● smoothens deployment process of creating new resources and updating them
● supported resource are Pods and Replication Controllers.
● while updating, it ensures sufficient capacity of new pod(s) available to serve
and deleting old ones.
Deployments
@girag

16. apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: appsvr-deployment
spec:
replicas: 3
template:
metadata:
labels:
app: appsvr
spec:
containers:
- name: appsvr
image: bm/appsvr:v1
ports:
- containerPort: 8080
Deployments
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: appsvr-deployment
spec:
replicas: 5
template:
metadata:
labels:
app: appsvr
spec:
containers:
- name: appsvr
image: bm/appsvr:v2
ports:
- containerPort: 8080
@girag

17. apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: appsvr-deployment
spec:
replicas: 3
template:
metadata:
labels:
app: appsvr
spec:
containers:
- name: appsvr
image: bm/appsvr:v1
ports:
- containerPort: 8080
Deployments
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: appsvr-deployment
spec:
replicas: 5
template:
metadata:
labels:
app: appsvr
spec:
containers:
- name: appsvr
image: bm/appsvr:v2
ports:
- containerPort: 8080
$ kubectl create -f dep.yaml
$ kubectl apply -f dep.yaml
@girag
creates 3 replica of
appsvr:v1 pods
update 3 pod with appsvr:v2
when no more outstanding load
&&
creates 2 more replica of appsvr:
v2 pods

18. ● introduced in v1.1
● part of extensions api
● small in size
● contains sensitive data like password, access-token, keys
● usage
○ file in mounted volume
○ used by kublet while pulling images to build pod
Secrets
@girag

19. apiVersion: v1
kind: Secret
metadata:
name: user-profile
type: Opaque
data:
user: graha
password: dmFsdWUtMQ0K
Secrets
apiVersion: v1
kind: Pod
metadata:
name: secret-access-pod
spec:
containers:
- name: tester
image: kubernetes/mounttest:0.1
command: [ "/mt", "--file_content=/etc/profile/user" ]
volumeMounts:
# name must match the volume name below
- name: profile
mountPath: /etc/profile
volumes:
- name: profile
secret:
secretName: user-profile
restartPolicy: Never
@girag

20. apiVersion: v1
kind: Secret
metadata:
name: user-profile
type: Opaque
data:
user: graha
password: dmFsdWUtMQ0K
Secrets
apiVersion: v1
kind: Pod
metadata:
name: secret-access-pod
spec:
containers:
- name: tester
image: kubernetes/mounttest:0.1
command: [ "/mt", "--file_content=/etc/profile/user" ]
volumeMounts:
# name must match the volume name below
- name: profile
mountPath: /etc/profile
volumes:
- name: profile
secret:
secretName: user-profile
restartPolicy: Never
@girag
creates a
secret store for
user-profile
mounted as file
system into
/etc/profile

21. ● introduced in v1
● part of core api
● flexible configuration model for k8s
● simplify storing configuration profile for application
● dynamic distribution of configuration
● usage
○ as environment variable
○ in volume
○ consistent data even from updating configuration model
ConfigMap
@girag

22. apiVersion: v1
kind: ConfigMap
metadata:
name: bm-env-config
data:
design-cache: 100
app-cache: 100
n-cmp-thread: 5
ConfigMap
@girag
apiVersion: v1
kind: Pod
metadata:
name: config-test-pod
spec:
containers:
- name: config-test-container
image: gcr.io/google_containers/busybox
command: [ "/bin/sh", "cat", "/etc/config/bm.env" ]
volumeMounts:
- name: config-volume
mountPath: /etc/config
volumes:
- name: config-volume
configMap:
name: bm-env-config
restartPolicy: Never

23. apiVersion: v1
kind: ConfigMap
metadata:
name: bm-env-config
data:
design-cache: 100
app-cache: 100
n-cmp-thread: 5
ConfigMap
@girag
apiVersion: v1
kind: Pod
metadata:
name: config-test-pod
spec:
containers:
- name: config-test-container
image: gcr.io/google_containers/busybox
command: [ "/bin/sh", "cat", "/etc/config/bm.env" ]
volumeMounts:
- name: config-volume
mountPath: /etc/config
volumes:
- name: config-volume
configMap:
name: bm-env-config
restartPolicy: Never
creates a
configuration store for
bm-env like secrets
mounted as file
system into
/etc/config

24. ● Locate our work
○ www.gopaddle.io
○ www.bluemeric.com
○ http://www.bluemeric.com/blog/
● Reach us
○ @bluemeric
○ http://www.bluemeric.com/contact/
Q&A
@girag