备案敏感信息
This commit is contained in:
@ -3,7 +3,7 @@ vssueId: 9
|
||||
layout: LearningLayout
|
||||
sharingTitle: 这里有一份最新的 K8S 教程,还可以免费在线答疑
|
||||
sidebarDepth: 0
|
||||
description: 本教程的主要依据是:Kubernetes官网文档,以及使用Kubernetes落地SpringCloud微服务并投产的实战经验,在线答疑。适用人群_ Kubernetes 初学者_学习过 Kubernetes,但在投产过程中仍有诸多疑虑和困惑的技术爱好者
|
||||
description: 本教程的主要依据是:Kubernetes文档,以及使用Kubernetes落地SpringCloud微服务并投产的实战经验,在线答疑。适用人群_ Kubernetes 初学者_学习过 Kubernetes,但在投产过程中仍有诸多疑虑和困惑的技术爱好者
|
||||
meta:
|
||||
- name: keywords
|
||||
content: K8S教程,K8S 教程,K8S培训,Kubernetes培训,K8S搭建,kuberntes搭建
|
||||
@ -38,7 +38,7 @@ meta:
|
||||
|
||||
## Kubernetes免费教程
|
||||
|
||||
本教程的主要依据是:Kubernetes 官网文档,以及使用 Kubernetes 落地 Spring Cloud 微服务并投产的实战经验。适用人群:
|
||||
本教程的主要依据是:Kubernetes 文档,以及使用 Kubernetes 落地 Spring Cloud 微服务并投产的实战经验。适用人群:
|
||||
* Kubernetes 初学者
|
||||
* 学习过 Kubernetes,但在投产过程中仍有诸多疑虑和困惑的技术爱好者
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/)。
|
||||
本文翻译自 Kubernetes [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/)。
|
||||
|
||||
Horizontal Pod Autoscaler 根据观察到的 CPU 利用率(或某些由应用程序提供的 [custom metrics](https://git.k8s.io/community/contributors/design-proposals/instrumentation/custom-metrics-api.md))自动调整控制器(Replication Controller / Deployment / ReplicaSet / StatefulSet)的 Pod 的数量。Horizontal Pod Autoscaler 不能应用于不可伸缩的对象,例如 DaemonSet。
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网文档 [Horizontal Pod Autoscaler Walkthrough](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/)
|
||||
本文翻译自 Kubernetes 文档 [Horizontal Pod Autoscaler Walkthrough](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/)
|
||||
|
||||
HorizontalPodAutoscaler 可以根据观察到的 CPU 利用率(或者 beta 阶段的其他应用程序提供的度量值)对 ReplicationController、Deployment、ReplicaSet、StatefulSet 中的 Pod 副本数执指定自动伸缩操作。
|
||||
|
||||
|
||||
11
learning/k8s-advanced/policy/psp.md
Normal file
11
learning/k8s-advanced/policy/psp.md
Normal file
@ -0,0 +1,11 @@
|
||||
---
|
||||
layout: LearningLayout
|
||||
description: Kubernetes教程_本文介绍了如何使用容器组安全策略来限定容器可以拥有的权限
|
||||
meta:
|
||||
- name: keywords
|
||||
content: Kubernetes教程, Pod Security Policies
|
||||
---
|
||||
|
||||
# 容器组安全策略
|
||||
|
||||
本文档翻译自 Kubernetes 文档 [Pod Security Policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/)
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Using kubectl to Create a Deployment](https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/) ,并有所改写
|
||||
本文翻译自 Kubernetes [Using kubectl to Create a Deployment](https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/) ,并有所改写
|
||||
|
||||
### 前提
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Viewing Pods and Nodes](https://kubernetes.io/docs/tutorials/kubernetes-basics/explore/explore-intro/) ,并有所改写
|
||||
本文翻译自 Kubernetes [Viewing Pods and Nodes](https://kubernetes.io/docs/tutorials/kubernetes-basics/explore/explore-intro/) ,并有所改写
|
||||
|
||||
## 目标
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Using a Service to Expose Your App](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/) ,并有所改写
|
||||
本文翻译自 Kubernetes [Using a Service to Expose Your App](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/) ,并有所改写
|
||||
|
||||
## 目标
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Learn Kubernetes Basics](https://kubernetes.io/docs/tutorials/kubernetes-basics/) ,并有所改写
|
||||
本文翻译自 Kubernetes [Learn Kubernetes Basics](https://kubernetes.io/docs/tutorials/kubernetes-basics/) ,并有所改写
|
||||
|
||||
相信很多初学者在入门 Kubernetes (以下简称k8s)时,都会被各种英文单词所困扰(例如:Deployment、Pod、Service等),这些名词在被翻译后也往往失去了原意,更不能体现出他们的相互关系。笔者在刚开始学习k8s时也遭遇到这种困境。但是,任何复杂的系统都是发源于最基本的公式或定理,k8s虽然庞大且复杂,不过只要抓住一些基本的脉络(一些最基本的组件的定义及使用),入门便也是毫不费劲。
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Running Multiple Instances of Your App](https://kubernetes.io/docs/tutorials/kubernetes-basics/scale/scale-intro/) ,并有所改写
|
||||
本文翻译自 Kubernetes [Running Multiple Instances of Your App](https://kubernetes.io/docs/tutorials/kubernetes-basics/scale/scale-intro/) ,并有所改写
|
||||
|
||||
## 目标
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文翻译自 Kubernetes 官网 [Performing a Rolling Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/) ,并有所改写
|
||||
本文翻译自 Kubernetes [Performing a Rolling Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/) ,并有所改写
|
||||
|
||||
## 目标
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网 [Assigning Pods to Nodes](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/)
|
||||
参考文档: Kubernetes [Assigning Pods to Nodes](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/)
|
||||
|
||||
## 概述
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网 [Managing Compute Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/)
|
||||
参考文档: Kubernetes [Managing Compute Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/)
|
||||
|
||||
## 概述
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
本文参考了 Kubernetes 官网 [Configure a Pod to Use a ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap),并有所改写
|
||||
本文参考了 Kubernetes [Configure a Pod to Use a ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap),并有所改写
|
||||
|
||||
Kubernetes ConfigMap 可以将配置信息和容器镜像解耦,以使得容器化的应用程序可移植。本文提供了一系列的实例,解释如何通过 Kuboard 创建 ConfigMap 以及如何使用 ConfigMap 中的数据配置 Pod(容器组)。
|
||||
|
||||
@ -25,7 +25,7 @@ Kubernetes ConfigMap 可以将配置信息和容器镜像解耦,以使得容
|
||||
## 创建 ConfigMap
|
||||
|
||||
::: tip 提示
|
||||
Kubernetes 官网描述了多种 ConfigMap 的创建方法,本文不再复述,请自行参考文档 [Configure a Pod to Use a ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap)
|
||||
Kubernetes 描述了多种 ConfigMap 的创建方法,本文不再复述,请自行参考文档 [Configure a Pod to Use a ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap)
|
||||
:::
|
||||
|
||||
* 打开 Kuboard 界面,并点击进入您想要创建 ConfigMap 的 **名称空间**
|
||||
|
||||
@ -12,7 +12,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
> 参考文档:Kubernetes 官网文档 [Configure a Security Context for a Pod or Container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#assign-selinux-labels-to-a-container)
|
||||
> 参考文档:Kubernetes 文档 [Configure a Security Context for a Pod or Container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#assign-selinux-labels-to-a-container)
|
||||
|
||||
Security Context(安全上下文)用来限制容器对宿主节点的可访问范围,以避免容器非法操作宿主节点的系统级别的内容,使得节点的系统或者节点上其他容器组受到影响。
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网文档 [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/)
|
||||
参考文档: Kubernetes 文档 [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/)
|
||||
|
||||
## 概述
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
> 参考文档: Kubernetes 官网文档 [Taints and Tolerations](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/)
|
||||
> 参考文档: Kubernetes 文档 [Taints and Tolerations](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/)
|
||||
|
||||
Pod 中存在属性 [Node selector / Node affinity](/learning/k8s-intermediate/config/assign-pod-node.html),用于将 Pod 指定到合适的节点。
|
||||
|
||||
|
||||
78
learning/k8s-intermediate/persistent/ceph/raspberry.md
Normal file
78
learning/k8s-intermediate/persistent/ceph/raspberry.md
Normal file
@ -0,0 +1,78 @@
|
||||
|
||||
# 在树莓派上安装 Ceph
|
||||
|
||||
## 安装 ubuntu
|
||||
|
||||
|
||||
|
||||
## 安装 docker
|
||||
|
||||
```sh
|
||||
wget https://repo.huaweicloud.com/docker-ce/linux/ubuntu/dists/focal/pool/stable/arm64/containerd.io_1.3.7-1_arm64.deb
|
||||
wget https://repo.huaweicloud.com/docker-ce/linux/ubuntu/dists/focal/pool/stable/arm64/docker-ce-cli_19.03.13~3-0~ubuntu-focal_arm64.deb
|
||||
wget https://repo.huaweicloud.com/docker-ce/linux/ubuntu/dists/focal/pool/stable/arm64/docker-ce_19.03.13~3-0~ubuntu-focal_arm64.deb
|
||||
dpkg -i containerd.io_1.3.7-1_arm64.deb docker-ce-cli_19.03.13~3-0~ubuntu-focal_arm64.deb docker-ce_19.03.13~3-0~ubuntu-focal_arm64.deb
|
||||
```
|
||||
|
||||
```sh
|
||||
sudo groupadd docker
|
||||
sudo usermod -aG docker $USER
|
||||
newgrp docker
|
||||
docker run hello-world
|
||||
```
|
||||
|
||||
|
||||
* 设置镜像地址
|
||||
|
||||
```sh
|
||||
sudo vim /etc/docker/daemon.json
|
||||
```
|
||||
* 添加 registry-mirrors 字段
|
||||
``` json
|
||||
{
|
||||
"registry-mirrors": ["https://05f073ad3c0010ea0f4bc00b7105ec20.mirror.swr.myhuaweicloud.com"]
|
||||
}
|
||||
```
|
||||
```sh
|
||||
systemctl restart docker
|
||||
```
|
||||
|
||||
## 安装 ceph
|
||||
|
||||
``` yaml
|
||||
[ceph]
|
||||
name=Ceph packages for $basearch
|
||||
baseurl=https://download.ceph.com/rpm-octopus/el7/$basearch
|
||||
enabled=1
|
||||
priority=2
|
||||
gpgcheck=1
|
||||
type=rpm-md
|
||||
gpgkey=https://download.ceph.com/keys/release.asc
|
||||
|
||||
|
||||
[ceph-noarch]
|
||||
name=Ceph noarch packages
|
||||
baseurl=https://download.ceph.com/rpm-octopus/el7/noarch
|
||||
enabled=1
|
||||
priority=2
|
||||
gpgcheck=1
|
||||
type=rpm-md
|
||||
gpgkey=https://download.ceph.com/keys/release.asc
|
||||
|
||||
|
||||
[ceph-source]
|
||||
name=Ceph source packages
|
||||
baseurl=https://download.ceph.com/rpm-octopus/el7/SRPMS
|
||||
enabled=0
|
||||
priority=2
|
||||
gpgcheck=1
|
||||
type=rpm-md
|
||||
gpgkey=https://download.ceph.com/keys/release.asc
|
||||
```
|
||||
|
||||
|
||||
|
||||
重置磁盘
|
||||
``` sh
|
||||
sgdisk --zap-all /dev/sda
|
||||
```
|
||||
@ -107,6 +107,6 @@ Kubernetes 对 Pod 进行调度时,以当时集群中各节点的可用资源
|
||||
|
||||
* 在场景中使用存储类
|
||||
|
||||
此时您可以在自己的场景中使用刚创建的存储类。Kuboard官网上,有以下几个地方可以用到NFS存储类:
|
||||
此时您可以在自己的场景中使用刚创建的存储类。Kuboard上,有以下几个地方可以用到NFS存储类:
|
||||
* [导入 example 微服务](/guide/example/import.html)
|
||||
* [安装监控套件](/guide/example/monitor.html#安装监控套件)
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网 [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/)
|
||||
参考文档: Kubernetes [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/)
|
||||
|
||||
## 存储类概述
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
> 参考文档: Kubernetes 官网文档 [Volumes](https://kubernetes.io/docs/concepts/storage/volumes/)
|
||||
> 参考文档: Kubernetes 文档 [Volumes](https://kubernetes.io/docs/concepts/storage/volumes/)
|
||||
|
||||
挂载是指将定义在 Pod 中的数据卷关联到容器,同一个 Pod 中的同一个数据卷可以被挂载到该 Pod 中的多个容器上。
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网文档 [Volumes](https://kubernetes.io/docs/concepts/storage/volumes/)
|
||||
参考文档: Kubernetes 文档 [Volumes](https://kubernetes.io/docs/concepts/storage/volumes/)
|
||||
|
||||
## 数据卷概述
|
||||
|
||||
|
||||
@ -119,7 +119,7 @@ Calico是Kubernetes生态系统中另一种流行的网络选择。虽然Flannel
|
||||
|
||||
|
||||
|
||||
[weave 官网](https://www.weave.works/oss/net/)
|
||||
[weave ](https://www.weave.works/oss/net/)
|
||||
|
||||
|
||||
Weave是由Weaveworks提供的一种Kubernetes CNI网络选项,它提供的模式和我们目前为止讨论的所有网络方案都不同。Weave在集群中的每个节点之间创建网状Overlay网络,参与者之间可以灵活路由。这一特性再结合其他一些独特的功能,在某些可能导致问题的情况下,Weave可以智能地路由。
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网文档 [Connecting Applications with Services](https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/)
|
||||
参考文档: Kubernetes 文档 [Connecting Applications with Services](https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/)
|
||||
|
||||
## Kubernetes 的网络模型
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档: Kubernetes 官网文档 [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
|
||||
参考文档: Kubernetes 文档 [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
|
||||
|
||||
本文介绍了 Kubernetes 中的 DNS 分配方式
|
||||
|
||||
|
||||
@ -13,8 +13,8 @@ meta:
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档:
|
||||
* Kubernetes 官网 [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)
|
||||
* Kubernetes 官网 [Ingress Controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
|
||||
* Kubernetes [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)
|
||||
* Kubernetes [Ingress Controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
|
||||
* Kubernetes Nginx Ingress Controller [Bare-metal considerations](https://kubernetes.github.io/ingress-nginx/deploy/baremetal/)
|
||||
* nginxinc/kubernets-ingress [kubernetes-ingress](https://github.com/nginxinc/kubernetes-ingress)
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档:Kubernetes 官网文档:[Service](https://kubernetes.io/docs/concepts/services-networking/service/)
|
||||
参考文档:Kubernetes 文档:[Service](https://kubernetes.io/docs/concepts/services-networking/service/)
|
||||
|
||||
## 创建 Service
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ meta:
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
参考文档:Kubernetes 官网文档:[Service](https://kubernetes.io/docs/concepts/services-networking/service/)
|
||||
参考文档:Kubernetes 文档:[Service](https://kubernetes.io/docs/concepts/services-networking/service/)
|
||||
|
||||
## 为何需要 Service
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ meta:
|
||||
|
||||
<AdSenseTitle>
|
||||
|
||||
> 参考文档: Kubernetes 官网 [Configure Pod Initialization](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-initialization/)
|
||||
> 参考文档: Kubernetes [Configure Pod Initialization](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-initialization/)
|
||||
|
||||
本文描述了如何为Pod配置初始化容器InitContainer。
|
||||
|
||||
@ -70,6 +70,6 @@ wget -O /work-dir/index.html https://kuboard.cn
|
||||
<!DOCTYPE html>
|
||||
<html lang="en" style="margin-right: 0px;"><head>
|
||||
<meta charset="utf-8">
|
||||
<title>Kuboard官网_Kubernetes教程_管理界面</title>
|
||||
<title>Kuboard_Kubernetes教程_管理界面</title>
|
||||
...
|
||||
```
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# 容器组_初始化容器
|
||||
|
||||
参考文档: Kubernetes 官网 [Init Containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/)
|
||||
参考文档: Kubernetes [Init Containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ meta:
|
||||
|
||||
<AdSenseTitle>
|
||||
|
||||
> 参考文档: Kubernetes 官网 [Debug Init Containers](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-init-containers/)
|
||||
> 参考文档: Kubernetes [Debug Init Containers](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-init-containers/)
|
||||
|
||||
本文描述了如何诊断初始化容器InitContainer在执行过程中的问题_本文中的命令行使用 `<pod-name>` 来指代Pod的名称_使用 `<init-container-1>` 和 `<init-container-2>` 来指代初始化容器的名称。
|
||||
|
||||
@ -103,4 +103,3 @@ kubectl logs <pod-name> -c <init-container-1>
|
||||
| `Init:CrashLoopBackOff` | Pod 中有一个初始化容器反复执行失败 |
|
||||
| `Pending` | Pod 还未开始执行初始化容器 |
|
||||
| `PodInitializing` or `Running` | Pod 已经完成初始化容器的执行 |
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# 容器组_生命周期
|
||||
|
||||
参考文档: Kubernetes 官网文档 [Pod Lifecycle](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/)
|
||||
参考文档: Kubernetes 文档 [Pod Lifecycle](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# DaemonSet 的替代选项
|
||||
|
||||
> 参考文档: Kubernetes 官网文档 [Alternatives to DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#alternatives-to-daemonset)
|
||||
> 参考文档: Kubernetes 文档 [Alternatives to DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#alternatives-to-daemonset)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# 与 DaemonSet 通信
|
||||
|
||||
> 参考文档 Kubernetes 官网文档 [Communicating with Daemon Pods](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#communicating-with-daemon-pods)
|
||||
> 参考文档 Kubernetes 文档 [Communicating with Daemon Pods](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#communicating-with-daemon-pods)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# 介绍 DaemonSet
|
||||
|
||||
> 参考文档: Kubernetes 官网文档 [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/)
|
||||
> 参考文档: Kubernetes 文档 [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# DaemonSet 是如何调度的
|
||||
|
||||
> 参考文档 Kubernetes 官网文档 [How Daemon Pods are Scheduled](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled)
|
||||
> 参考文档 Kubernetes 文档 [How Daemon Pods are Scheduled](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# 更新 DaemonSet
|
||||
|
||||
> 参考文档 Kubernetes 官网文档 [Updating a DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#updating-a-daemonset)
|
||||
> 参考文档 Kubernetes 文档 [Updating a DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#updating-a-daemonset)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# 介绍 Deployment
|
||||
|
||||
参考文档: Kubernetes 官网 [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)、 [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)
|
||||
参考文档: Kubernetes [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)、 [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
@ -63,7 +63,7 @@ ReplicaSet 副本集的主要几个字段有:
|
||||
|
||||
副本集将通过创建、删除 Pod 容器组来确保符合 selector 选择器的 Pod 数量等于 replicas 指定的数量。当符合 selector 选择器的 Pod 数量不够时,副本集通过使用 template 中的定义来创建 Pod。
|
||||
|
||||
在 Kubernetes 中,并不建议您直接使用 ReplicaSet,推荐使用 Deployment,由 Deployment 创建和管理 ReplicaSet。 关于副本集的更多信息,请参考 Kubernetes 官网文档 [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)
|
||||
在 Kubernetes 中,并不建议您直接使用 ReplicaSet,推荐使用 Deployment,由 Deployment 创建和管理 ReplicaSet。 关于副本集的更多信息,请参考 Kubernetes 文档 [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)
|
||||
|
||||
## Deployment 概述
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ meta:
|
||||
|
||||
# StatefulSet 的使用场景
|
||||
|
||||
> 参考文档: Kubernetes 官网文档 [StatefulSets](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/)
|
||||
> 参考文档: Kubernetes 文档 [StatefulSets](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/)
|
||||
|
||||
<AdSenseTitle/>
|
||||
|
||||
|
||||
@ -51,7 +51,7 @@ Kuboard 在落地 Spring Cloud 微服务的过程中,设计了如下图所示
|
||||
|
||||
| 参与方 | 渠道 | 展现层项目 |
|
||||
| ---------- | ---------- | ---------------- |
|
||||
| 散客 | PC浏览器 | 官网 |
|
||||
| 散客 | PC浏览器 | |
|
||||
| | 移动站 | 移动站 |
|
||||
| | 微信小程序 | 微信小程序 |
|
||||
| | App | APP |
|
||||
|
||||
@ -68,7 +68,7 @@ yum install java-1.8.0-openjdk\* -y
|
||||
|
||||
## 在 master 节点上安装 maven
|
||||
|
||||
* 在 [maven 官网](http://maven.apache.org/download.cgi) 获取最新版 maven 的 binary 文件下载链接,例如 apache-maven-3.6.2-bin.tar.gz 的下载地址为 `http://mirrors.tuna.tsinghua.edu.cn/apache/maven/maven-3/3.6.2/binaries/apache-maven-3.6.2-bin.tar.gz`
|
||||
* 在 [maven ](http://maven.apache.org/download.cgi) 获取最新版 maven 的 binary 文件下载链接,例如 apache-maven-3.6.2-bin.tar.gz 的下载地址为 `http://mirrors.tuna.tsinghua.edu.cn/apache/maven/maven-3/3.6.2/binaries/apache-maven-3.6.2-bin.tar.gz`
|
||||
|
||||
* 以 root 身份在 master 节点上执行:
|
||||
```sh
|
||||
|
||||
1
learning/k8s-practice/redis/redis.md
Normal file
1
learning/k8s-practice/redis/redis.md
Normal file
@ -0,0 +1 @@
|
||||
https://rancher.com/blog/2019/deploying-redis-cluster
|
||||
Reference in New Issue
Block a user