5. Closing the distance
Nucleo is a platform that help developers can
stay focused on development.
and Nucleo will take over the rest things such
as Resource pooling, Continuous delivery,
Rollback, Scaling, Auto scaling, Logging,
Metering, Alerting, DNS, SSL, Event, Service
Discovery...
9. Read manual rst if you can
but, tl;dr
http://leoh0.github.io/images/kubernetes-
documents.pdf
10. So today I speak only about...
ingress
persistent volume
custom resource de nition
11. before speak ingress(L7)
service (L4) publishing types
ClusterIP <- internal ip
NodePort <- all nodes need to open that port
LoadBalancer <- need to cloud provider
ExternalName <- CNAME
13. auto con gured con g in
ingress nginx controller
upstream kube-system-dashboard-80 {
#(...configs...)
server 192.168.63.221:8080 max_fails=0;
server 192.168.68.26:8080 max_fails=0;
}
server {
server_name dashboard-kube-system-nucleo.local.com;
listen [::]:80;
location / {
#(...configs...)
proxy_pass http://kube-system-dashboard-80;
}
}
20. how to make ingress node
1. setup ingress node rst just like other nodes
2. setup labels to ingress node (enable scheduling
ingress pods)
3. setup taints to ingress node (disable scheduling
other pods)
4. install nginx-ingress-controller by hostnetwork
daemonset with node selector and tolerations
29. custom resource de nition
A built-in API that offers a simple way to create
custom resources .
ThirdPartyResource(TPR) ->
CustomResourceDe nition(CRD)
TPR is deprecated at k8s < 1.8.0
CRD is begin at k8s > 1.7.0
30. resources
A resource is an endpoint in the Kubernetes API
that stores a collection of API objects of a certain
kind.
DaemonSet , Deployment , Job , Pod , ReplicaSet ,
ReplicationController , StatefulSet , Ingress , Service ,
ConfigMap , Secret , PersistentVolumeClaim ,
StorageClass , Volume , Event , HorizontalPodAutoscaler ,
PodPreset , ...
31. custom resources
make your own resource dynamically
and use k8s database, API, authentication like the
other resource objects
support CRUD functions e.g. Create , Update , Delete
, Get , and List
32. custom controllers
The controller interprets the structured data as a
record of the user’s desired state, and continually
takes action to achieve and maintain that state.
e.g. kube-controller-manager , rbd-provisioner ,
operator , ...
can work with any kind of resource, but they are
especially effective when combined with
custom resources .