fanux / fanux.github.io Goto Github PK

https://sealyun.com/post/kube-scheduler-source-code/

kubernetes集群三步安装 kube-scheduler源码分析 调度器扩展 定制化调度器有三种方式： 改scheduler代码重新编译 - 没啥

https://sealyun.com/post/docker-network/

网络概述 端口映射： $ docker run -p 8080:80 nginx:latest 如果没有这个-p，会发现启动了nginx但是无法通过宿主机访问到web服务，而使用了-p参数后就可以通过访问主

https://sealyun.com/post/kubeadm-dev/

kubernetes集群三步安装 修改kubeadm证书过期时间 本文通过修改kubeadm源码让kubeadm默认的一年证书过期时间修改为99

https://sealyun.com/post/etcd-manage/

广告 | kubernetes各版本离线安装包 etcd 证书配置 证书生成 cfssl安装： mkdir ~/bin curl -s -L -o ~/bin/cfssl https://pkg.cfssl.org/R1.2/cfssl_linux-amd64 curl -s -L -o ~/bin/cfssljson https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64 chmod +x /bin/{cfssl,cfssljson} export PATH=$PATH:/bin mkdir ~/cfssl cd ~/cfssl 写入如下json文

https://sealyun.com/post/dotscale-2014-as-a-sketch/

https://sealyun.com/pro/products

http://sealyun.com/post/sealyun-k8s-offline/

k8s离线包解析 产品地址 鸣谢 大家好，首先感谢大家对我们产品的支持，特别是一些老客户的持续支持，让我可以有动力把这个事情持续进行下去。 感谢大家

http://sealyun.com/post/istio-quickstart/

广告 | kubernetes各版本离线安装包 祝贺istio1.0发布, 在此献上教程一份 安装 安装k8s 强势插播广告 三步安装，不多说 安装helm,

kubectl describe pod kube-dns-545bc4bfd4-dl5wr -n kube-system
Name: kube-dns-545bc4bfd4-dl5wr
Namespace: kube-system
Node: slave1/11.85.198.45
Start Time: Mon, 20 Nov 2017 04:24:27 -0500
Labels: k8s-app=kube-dns
pod-template-hash=1016706980
Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"kube-system","name":"kube-dns-545bc4bfd4","uid":"9b209da2-cdd4-11e7-82ef-e8611f1b...
Status: Running
IP: 192.168.140.193
Created By: ReplicaSet/kube-dns-545bc4bfd4
Controlled By: ReplicaSet/kube-dns-545bc4bfd4
Containers:
kubedns:
Container ID: docker://9457133785e0fe1299334c58ca6a5a2ef1ad097921e95679775b3c417a84f0bc
Image: gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5
Image ID: docker://sha256:512cd7425a731bee1f2a3e4c825fc1cfe516c8b7905874f24bee6da12801d663
Ports: 10053/UDP, 10053/TCP, 10055/TCP
Args:
--domain=cluster.local.
--dns-port=10053
--config-dir=/kube-dns-config
--v=2
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: ContainerCannotRun
Message: oci runtime error: container_linux.go:265: starting container process caused "process_linux.go:284: applying cgroup configuration for process caused "No such device or address""

  Exit Code:    128
  Started:      Mon, 20 Nov 2017 10:12:11 -0500
  Finished:     Mon, 20 Nov 2017 10:12:11 -0500
Ready:          False
Restart Count:  72
Limits:
  memory:  170Mi
Requests:
  cpu:      100m
  memory:   70Mi
Liveness:   http-get http://:10054/healthcheck/kubedns delay=60s timeout=5s period=10s #success=1 #failure=5
Readiness:  http-get http://:8081/readiness delay=3s timeout=5s period=10s #success=1 #failure=3
Environment:
  PROMETHEUS_PORT:  10055
Mounts:
  /kube-dns-config from kube-dns-config (rw)
  /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-hnp49 (ro)

dnsmasq:
Container ID: docker://518ef274674ae2b3a8428bd4eabdec57789fd77518bf264c9641abe403fbcbb8
Image: gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5
Image ID: docker://sha256:459944ce8cc4f08ebade5c05bb884e4da053d73e61ec6afe82a0b1687317254c
Ports: 53/UDP, 53/TCP
Args:
-v=2
-logtostderr
-configDir=/etc/k8s/dns/dnsmasq-nanny
-restartDnsmasq=true
--
-k
--cache-size=1000
--log-facility=-
--server=/cluster.local/127.0.0.1#10053
--server=/in-addr.arpa/127.0.0.1#10053
--server=/ip6.arpa/127.0.0.1#10053
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Mon, 20 Nov 2017 10:12:11 -0500
Finished: Mon, 20 Nov 2017 10:14:21 -0500
Ready: False
Restart Count: 78
Requests:
cpu: 150m
memory: 20Mi
Liveness: http-get http://:10054/healthcheck/dnsmasq delay=60s timeout=5s period=10s #success=1 #failure=5
Environment:
Mounts:
/etc/k8s/dns/dnsmasq-nanny from kube-dns-config (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-hnp49 (ro)
sidecar:
Container ID: docker://9708c84584f2cdbcf527f919ce9206174c9c7e32f8e36c52ddca340e1736204a
Image: gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.5
Image ID: docker://sha256:fed89e8b4248a788655d528d96fe644aff012879c782784cd486ff6894ef89f6
Port: 10054/TCP
Args:
--v=2
--logtostderr
--probe=kubedns,127.0.0.1:10053,kubernetes.default.svc.cluster.local,5,A
--probe=dnsmasq,127.0.0.1:53,kubernetes.default.svc.cluster.local,5,A
State: Running
Started: Mon, 20 Nov 2017 04:24:34 -0500
Ready: True
Restart Count: 0
Requests:
cpu: 10m
memory: 20Mi
Liveness: http-get http://:10054/metrics delay=60s timeout=5s period=10s #success=1 #failure=5
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-hnp49 (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
kube-dns-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: kube-dns
Optional: true
kube-dns-token-hnp49:
Type: Secret (a volume populated by a Secret)
SecretName: kube-dns-token-hnp49
Optional: false
QoS Class: Burstable
Node-Selectors:
Tolerations: CriticalAddonsOnly
node-role.kubernetes.io/master:NoSchedule
node.alpha.kubernetes.io/notReady:NoExecute for 300s
node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message

Normal Killing 41m (x70 over 5h) kubelet, slave1 Killing container with id docker://dnsmasq:Container failed liveness probe.. Container will be killed and recreated.
Warning Unhealthy 11m (x309 over 5h) kubelet, slave1 Liveness probe failed: HTTP probe failed with statuscode: 503
Warning BackOff 1m (x1629 over 5h) kubelet, slave1 Back-off restarting failed container

https://sealyun.com/post/sealos/

kubernetes集群三步安装 构建生产环境可用的高可用kubernetes集群 | sealos项目地址 特性 支持任意节点的etcd集群自动构建

https://sealyun.com/post/k8s-ipvs/

kubernetes启用ipvs 确保内核开启了ipvs模块 [root@k8s ~]# lsmod|grep ip_vs ip_vs_sh 12688 0 ip_vs_wrr 12697 0 ip_vs_rr 12600 16 ip_vs 141092 23 ip_vs_rr,ip_vs_sh,xt_ipvs,ip_vs_wrr nf_conntrack 133387 9 ip_vs,nf_nat,nf_nat_ipv4,nf_nat_ipv6,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_netlink,nf_conntrack_ipv4,nf_conntrack_ipv6 libcrc32c 12644 3 ip_vs,nf_nat,nf_conntrack 没开启加载方式: modprobe -- ip_vs modprobe -- ip_vs_rr modprobe --

https://sealyun.com/post/heapster-error/

kubernetes集群三步安装 kubernetes1.12.0版本dashboard使用heapster无法正常显示监控数据 查看heaps

https://sealyun.com/post/kube-dev/

广告 | kubernetes离线安装包，仅需三步 初始化客户端 这里给了两种初始化kubernetes客户端的方式，一种根据kubeconfig文

http://sealyun.com/post/sealyun-k8s-offline/?code=7f309507407c4ede5f3b

k8s离线包解析 产品地址 鸣谢 大家好，首先感谢大家对我们产品的支持，特别是一些老客户的持续支持，让我可以有动力把这个事情持续进行下去。 感谢大家

http://sealyun.com/post/k8s-rbac/

kubernetes RBAC实战 环境准备 先用kubeadm安装好kubernetes集群，包地址在此 好用又方便，服务周到，童叟无欺 本文目的，让名为devuse

https://sealyun.com/post/docker-network/

网络概述 端口映射： $ docker run -p 8080:80 nginx:latest 如果没有这个-p，会发现启动了nginx但是无法通过宿主机访问到web服务，而使用了-p参数后就可以通过访问主

https://sealyun.com/post/kubeadm/

kubernetes集群三步安装 kubeadm 1.13版本 此版本更新了不少东西，以前老的配置不再适用 W1205 19:10:23.541054 58540 strict.go:54] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta1", Kind:"InitConfiguration"}: error unmarshaling JSON: while decoding JSON: json: unknown field your configuration file uses an old API

https://sealyun.com/post/ci-cd/

kubernetes集群三步安装 CI 概述 用一个可描述的配置定义整个工作流 程序员是很懒的动物，所以想各种办法解决重复劳动的问题，如果你的工作流中

https://sealyun.com/post/heapster-error/

kubernetes集群三步安装 kubernetes1.12.0版本dashboard使用heapster无法正常显示监控数据 查看heaps

https://sealyun.com/post/calico/

calico 网络原理 node节点 装网络之前路由 [root@iZj6c3cqwumhn5jov661z7Z ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.31.255.253 0.0.0.0 UG 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.31.240.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 网卡： [root@iZj6c3cqwumhn5jov661z7Z

https://sealyun.com/post/kube-proxy-src/

kube-proxy源码解析 ipvs相对于iptables模式具备较高的性能与稳定性, 本文讲以此模式的源码解析为主，如果想去了解iptabl