mirror of
https://github.com/wahyd4/knowledge.git
synced 2026-08-16 16:46:21 +10:00
extract kubernetes.md
This commit is contained in:
@@ -14,6 +14,7 @@
|
||||
- [Testing](categories/testing.md)
|
||||
- [Devops](categories/devops.md)
|
||||
- [Docker](categories/devops/docker.md)
|
||||
- [Kubernetes](categories/devops/kubernetes.md)
|
||||
- [Incident Management](categories/devops/incident.md)
|
||||
- [Linux](categories/devops/linux.md)
|
||||
- [Web](categories/web.md)
|
||||
|
||||
@@ -3,90 +3,21 @@
|
||||
## Rancher
|
||||
|
||||
Easy to use, just drag and drop things.
|
||||
## Kubernetes
|
||||
|
||||
- Pod
|
||||
- Single container
|
||||
- Multiple containers
|
||||
- share ip
|
||||
- share volumes
|
||||
- Node
|
||||
- Service
|
||||
- ClusterIP (default)
|
||||
- NodePort （ access by port）
|
||||
- LoadBalancer (external ip)
|
||||
- ExternalName dns
|
||||
- Deployment
|
||||
- Replica Set
|
||||
- Service rolling update
|
||||
- DaemonSet
|
||||
- running a cluster storage daemon, such as glusterd, ceph, on each node
|
||||
- running a logs collection daemon on every node, such as fluentd or logstash.
|
||||
- running a node monitoring daemon on every node, such as Prometheus Node Exporter, collectd, New Relic agent, or Ganglia gmond.
|
||||
- StatefulSets
|
||||
- Ordered, graceful deployment and scaling
|
||||
- Stable, persistent storage.
|
||||
- Stable, unique network identifiers.
|
||||
- Ordered, graceful deletion and termination.
|
||||
- Proxy
|
||||
- DNS
|
||||
- service.namespace
|
||||
- Secrets
|
||||
- Persistent volumes
|
||||
- Available
|
||||
- a free resource that is not yet bound to a claim
|
||||
- Bound
|
||||
- the volume is bound to a claim
|
||||
- Released
|
||||
- the claim has been deleted, but the resource is not yet reclaimed by the cluster
|
||||
- Failed
|
||||
- the volume has failed its automatic reclamation
|
||||
## [Kubernetes](kubernetes.md)
|
||||
|
||||
### Several ways to access a service inside Kubernetes cluster
|
||||
* ClusterIP, Can only be accessed inside the cluster. You can access inside `kubectl proxy`
|
||||
* NodePort, You can access the service by a specific public port between `30000–32767`, if the cluster server IP changes, then your service' endpoint url changes.
|
||||
* LoadBalancer, it's kind of external service, all the requests go through the loadbalancer. Every service needs a new IP for this.
|
||||
* Ingress, can be shared among multiple services, you can have different types of ingress controllers: gec, nginx, contour,istio and so on.
|
||||
Which is the actual standard orchestration platform.
|
||||
|
||||
Links:
|
||||
* [Kubernetes NodePort vs LoadBalancer vs Ingress? When should I use what?](https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0)
|
||||
|
||||
### Zero down time deployment
|
||||
Set strategy type to `RollingUpdate` instead of `Recreate`
|
||||
```yaml
|
||||
spec:
|
||||
replicas: 1
|
||||
strategy:
|
||||
type: RollingUpdate
|
||||
rollingUpdate:
|
||||
maxUnavailable: 50%
|
||||
maxSurge: 1
|
||||
```
|
||||
## Some useful commands
|
||||
|
||||
```bash
|
||||
|
||||
kubectl config set-context context-name --namespace default-namespace-name #default active context
|
||||
kubectl config view #view config
|
||||
kubectl get nodes #get nodes
|
||||
kubectl get namespaces #get all namespaces
|
||||
kubectl get pods #get pods
|
||||
kubectl get deployments #get deployments
|
||||
kubectl get services #get services
|
||||
kubectl get ingress #get ingresses
|
||||
|
||||
```
|
||||
|
||||
# Benefits
|
||||
## Benefits of using Docker
|
||||
|
||||
- escape the app dependency matrix
|
||||
- Solve the environment issue. it works on my machine.
|
||||
# Network
|
||||
## Network
|
||||
|
||||
- Bridge
|
||||
- Host
|
||||
|
||||
# Tips
|
||||
## Tips
|
||||
|
||||
- difference between `cmd` and `entrypoint`
|
||||
- difference between `copy` and `add`
|
||||
|
||||
@@ -0,0 +1,92 @@
|
||||
## Kubernetes
|
||||
|
||||
- Pod
|
||||
- Single container
|
||||
- Multiple containers
|
||||
- share ip
|
||||
- share volumes
|
||||
- Node
|
||||
- Service
|
||||
- ClusterIP (default)
|
||||
- NodePort （ access by port）
|
||||
- LoadBalancer (external ip)
|
||||
- ExternalName dns
|
||||
- Deployment
|
||||
- Replica Set
|
||||
- Service rolling update
|
||||
- DaemonSet
|
||||
- running a cluster storage daemon, such as glusterd, ceph, on each node
|
||||
- running a logs collection daemon on every node, such as fluentd or logstash.
|
||||
- running a node monitoring daemon on every node, such as Prometheus Node Exporter, collectd, New Relic agent, or Ganglia gmond.
|
||||
- StatefulSets
|
||||
- Ordered, graceful deployment and scaling
|
||||
- Stable, persistent storage.
|
||||
- Stable, unique network identifiers.
|
||||
- Ordered, graceful deletion and termination.
|
||||
- Proxy
|
||||
- DNS
|
||||
- service.namespace
|
||||
- Secrets
|
||||
- Persistent volumes
|
||||
- Available
|
||||
- a free resource that is not yet bound to a claim
|
||||
- Bound
|
||||
- the volume is bound to a claim
|
||||
- Released
|
||||
- the claim has been deleted, but the resource is not yet reclaimed by the cluster
|
||||
- Failed
|
||||
- the volume has failed its automatic reclamation
|
||||
|
||||
### Several ways to access a service inside Kubernetes cluster
|
||||
* ClusterIP, Can only be accessed inside the cluster. You can access inside `kubectl proxy`
|
||||
* NodePort, You can access the service by a specific public port between `30000–32767`, if the cluster server IP changes, then your service' endpoint url changes.
|
||||
* LoadBalancer, it's kind of external service, all the requests go through the loadbalancer. Every service needs a new IP for this.
|
||||
* Ingress, can be shared among multiple services, you can have different types of ingress controllers: gec, nginx, contour,istio and so on.
|
||||
|
||||
Links:
|
||||
* [Kubernetes NodePort vs LoadBalancer vs Ingress? When should I use what?](https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0)
|
||||
|
||||
### Zero down time deployment
|
||||
Set strategy type to `RollingUpdate` instead of `Recreate`
|
||||
```yaml
|
||||
spec:
|
||||
replicas: 1
|
||||
strategy:
|
||||
type: RollingUpdate
|
||||
rollingUpdate:
|
||||
maxUnavailable: 50%
|
||||
maxSurge: 1
|
||||
```
|
||||
|
||||
### Some useful commands
|
||||
|
||||
```bash
|
||||
|
||||
kubectl config set-context context-name --namespace default-namespace-name #default active context
|
||||
kubectl config view #view config
|
||||
kubectl get nodes #get nodes
|
||||
kubectl get namespaces #get all namespaces
|
||||
kubectl get pods #get pods
|
||||
kubectl get deployments #get deployments
|
||||
kubectl get services #get services
|
||||
kubectl get ingress #get ingresses
|
||||
|
||||
```
|
||||
|
||||
### Kubernetes Dashboard
|
||||
|
||||
#### Deploy Dashboard
|
||||
|
||||
```bash
|
||||
kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml
|
||||
```
|
||||
#### Access dashboard
|
||||
|
||||
```bash
|
||||
# First fetch cluster info, make sure cluster is running properly
|
||||
kubectl cluster-info
|
||||
|
||||
# Normally the url for dashboard would be
|
||||
http://your_ip:8080/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/
|
||||
|
||||
```
|
||||
Reference in New Issue
Block a user