## 1.查看默认的命名空间的pod

![image.png](/static/img/25526ff3d20bd1259ea990daa499fdad.image.webp)
```js
kubectl get pod
```
## 2.查看所有的命名空间的pod

![image.png](/static/img/a737c3ea077d0bc3a779568d8c861e3a.image.webp)
```js
kubectl get pod
```
## 3.查看所有命名空间的pod的详细信息

![image.png](/static/img/791f187500b01a6b5a827c206f426c32.image.webp)
```js
kubectl get pod -o wide -A
```

## 4.查看指定命名空间的pod的详细信息

![image.png](/static/img/c0fe44d0fcfc75cdab9a5ef1b25ae73d.image.webp)

```js
kubectl get pod -o wide -n 命名空间的名称
```

## 5.实时监控pod的状态

![image.png](/static/img/454d635e525076d1282bde9cd0a5c81c.image.webp)

```js
kubectl get pod -w -n 命名空间的名称
```


## 6.简单创建一个pod命令

![image.png](/static/img/1e93b5678d5f6815776bc3418f754285.image.webp)
```js
kubectl run pod的名称 --image=nginx
```

## 7.查看pod错误描述信息

![image.png](/static/img/aaa69a2318812ec1dc6eb0a07cbec33b.image.webp)

```js
kubectl describe pod nginx
```
该问题是拉取镜像失败了，需要重新配置一下containerd容器镜像拉取地址

```js
vim /etc/containerd/config.toml
```
```js
disabled_plugins = ["restart"]
[plugins.linux]
shim_debug = true

[plugins.cri.registry.mirrors."docker.io"]
endpoint = [
    "https://docker.m.daocloud.io",
    "https://docker.1panel.live",
    "https://hub.rat.dev",
    "https://registry-1.docker.io"  # 官方源保底
]

[plugins.cri]
sandbox_image = "registry.aliyuncs.com/google_containers/pause:3.2"
```
```js
#重启容器
systemctl restart containerd
```
然后测试一下拉取还是报错，看来是crictl问题

![image.png](/static/img/264a23020221aa72856be3645a1f5de9.image.webp)
需要创建/修改 crictl 配置文件

```js
mkdir -p /etc/crictl
cat <<EOF | sudo tee /etc/crictl/config.yaml
runtime-endpoint: unix:///run/containerd/containerd.sock
image-endpoint: unix:///run/containerd/containerd.sock
timeout: 10
debug: true
EOF
```
再次查看NG镜像已经拉取成功

![image.png](/static/img/b1a7cf9477f80e52b899750383f6fbc0.image.webp)

## 8.以yml文件方式创建pod

![image.png](/static/img/ff69c69b6e10cbf9cbcfae68343afbee.image.webp)

```js
vi k8s.yml
```

```yml
apiVersion: v1
kind: Pod
metadata:
  name: nginx
  labels:
    app: nginx
spec:
  containers:
    - name: nginx
      image: nginx:1.21
      imagePullPolicy: IfNotPresent
  restartPolicy: Always
```

```js
kubectl apply -f k8s.yml
```

## 9.删除pod

```js
kubectl delete pod <pod的名称>
kubectl delete -f k8s.yml
```

## 10.进入pod容器

![image.png](/static/img/fc21030d2ac36624421680530879d498.image.webp)

```js
kubectl exec -it nginx -- bash
```

如果一个pod有多个容器，列如：nginx-container + log-collector

```js
# 进入名为 nginx-container 的容器
kubectl exec -it nginx -c nginx-container -- bash

# 进入名为 log-collector 的容器
kubectl exec -it nginx -c log-collector -- bash
```

## 11.查看pod容器日志

![image.png](/static/img/bc0cf978b1fc52ae70dc3fd78002c687.image.webp)
```js
#查看该pod所有容器的日志
kubectl logs -f <pod名称>

#查看该pod指定容器的日志
kubectl logs -f <pod名称>  -c log-collector
```

## 12.查看pod的标签

![image.png](/static/img/15d1c2565e9deddf833872e3d0c45256.image.webp)

![image.png](/static/img/4cdc64cb6f17b6509d75429a3ab5b359.image.webp)
```js
#查看pod的标签
kubectl get pod --show-labels
```
## 13.添加pod的标签

![image.png](/static/img/15910632cf7d20ef54862986a03ece0a.image.webp)
```js
kubectl label pod nginx-redis01 name=songxuan
```
## 14.修改pod标签值
![](http://songxuan.vip/static/img/15910632cf7d20ef54862986a03ece0a.image.webp)

```js
kubectl label --overwrite pod nginx-redis01 name=xuan
```

## 15.删除pod的标签

![image.png](/static/img/45777d570ccc903475ac08459c31c8c7.image.webp)
```js
kubectl label pod nginx-redis01 name-
```

2.pod的操作命令


```js

macro = "your_macro_name"  -- 替换为录制的宏名称(纯英文)
kaiguan = "ctrl"
state = 0

function OnEvent(event, arg)
    if event == "PROFILE_ACTIVATED" then
        while true do
            if IsModifierPressed(kaiguan) and state == 0 then
                state = 1
                PlayMacro(macro)
                
                while IsModifierPressed(kaiguan) do
                    -- 等待按键释放
                end
            elseif IsModifierPressed(kaiguan) and state == 1 then
                state = 0
                AbortMacro()
                while IsModifierPressed(kaiguan) do
                    -- 等待按键释放
                end
            end
            Sleep(10)  -- 防止CPU占用过高
        end
    end
end

```

lua脚本宏配置

# 一、虚拟机网络配置
# 二、环境准备

1. 关闭防火墙



临时关闭防火墙
```js
systemctl stop firewalld
```
永久关闭防火墙

```js
systemctl disable firewalld
```
2. 关闭内存交换分区

```js
swapoff -a
```

```js
vim /etc/fstab
# 注释 swap 行
```
3.关闭selinux

```js
setenforce 0	
```
4.同步服务器时间

```js
yum install ntpdate -t
ntpdate -u ntp.aliyun.com
```



![image.png](/static/img/25465d0d9f27a181b17e7d8685d38c78.image.webp)


![image.png](/static/img/f03f80673a747a7f9e4b121ec3dbeb67.image.webp)

![image.png](/static/img/927acc1b01e629b0d5e101116b58fd0d.image.webp)

# 三、配置虚拟机静态IP

```js
cd /etc/sysconfig/network-scripts
```
1. 修改网络配置
![image.png](/static/img/b78dbf0bf13f6024e10a5de99d9f8597.image.webp)
```js
vi ifcfg-配置_1
```

![image.png](/static/img/81c5b3a4655798efd5cc06812dc8bb57.image.webp)

2.修改完成后重启网卡

```js
service network restart
```
# 四、配置好三台虚拟机
1. IP为：192.168.201.100、192.168.201.101、192.168.201.102、192.168.201.103
2. 修改主机名加入host中

```js
hostnamectl set-hostname  k8s-Master01
hostnamectl set-hostname  k8s-node01
hostnamectl set-hostname  k8s-node02
hostnamectl set-hostname  k8s-register
```

```js
cat >> /etc/hosts <<EOF
192.168.201.100 k8s-Master01
192.168.201.101  k8s-node01
192.168.201.102  k8s-node02
192.168.201.103  k8s-register
EOF
```
3. 由于centos7原来的yum源使用不了，需要修改yum源
先进行备份yum源文件

```js
cd /etc/yum.repos.d/
mkdir backup
mv *.repo backup/
```
4. 配置阿里云镜像源

```js
wget -O /etc/yum.repos.d/CentOS-Base.repo https://mirrors.aliyun.com/repo/Centos-7.repo
```
5. 重新建立缓存

```js
yum clean all
yum makecache
```
# 五、安装containerd
1. 安装 yum-config-manager 相关依赖

```js
yum install -y yum-utils device-mapper-persistent-data lvm2
```
2. 添加 containerd yum 源

```js
yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
```
3. 安装 containerd

```js
yum install  -y containerd.io cri-tools  
```
4. 配置 containerd

```js
cat >  /etc/containerd/config.toml <<EOF
disabled_plugins = ["restart"]
[plugins.linux]
shim_debug = true
[plugins.cri.registry.mirrors."docker.io"]
endpoint = ["https://frz7i079.mirror.aliyuncs.com"]
[plugins.cri]
sandbox_image = "registry.aliyuncs.com/google_containers/pause:3.2"
EOF
```
5. 启动 containerd 服务 并 开机配置自启动

```js
systemctl enable containerd && systemctl start containerd && systemctl status containerd
```
6. 配置 containerd 配置

```js
cat > /etc/modules-load.d/containerd.conf <<EOF
overlay
br_netfilter
EOF
```
7. 配置 k8s 网络配置

```js
cat  > /etc/sysctl.d/k8s.conf <<EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
EOF
```
8. 加载 overlay br_netfilter 模块

```js
modprobe overlay
modprobe br_netfilter
```
9. 查看当前配置是否生效

```js
sysctl -p /etc/sysctl.d/k8s.conf
```

# 六、安装K8S集群
1. 添加源

```js
yum repolist
```

```js
cat <<EOF > kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
```


```js
mv kubernetes.repo /etc/yum.repos.d
```

2. 安装 k8s

```js
# 安装最新版本
yum install -y kubelet kubeadm kubectl

# 指定版本安装
yum install -y kubelet-1.26.0 kubectl-1.26.0 kubeadm-1.26.0

# 启动 kubelet
systemctl enable kubelet && sudo systemctl start kubelet && sudo systemctl status kubelet
```

3. 初始化集群，注意！！！只需要控制节点执行（master节点）。

:::note{title="注意"}
注意: 初始化 k8s 集群仅仅需要再在 master 节点进行集群初始化!
:::


```js
kubeadm init \
--apiserver-advertise-address=192.168.201.100 \
--pod-network-cidr=10.244.0.0/16 \
--image-repository registry.aliyuncs.com/google_containers \
--cri-socket=unix:///var/run/containerd/containerd.sock
```
4. 初始化完成后，使用工作节点加入集群

![image.png](/static/img/c2182f9bcb317799dbf4d44ae7254d72.image.webp)
![image.png](/static/img/0063c5cab486da19f250b489e11d8686.image.webp)

```js
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
```
5. 使用截图的秘钥加入K8S集群
```js
kubeadm join 192.168.201.100:6443 --token n78quj.0nbr6yv0qr74pq6h \
        --discovery-token-ca-cert-hash sha256:a4e2aec71acd6d66d80fea93fad446ae5a3f78ab024ef59c8560c6b861451d31
```

:::info{title="相关信息"}
如加入配置失败，可以清理配置文件后重新加入
执行重置命令


kubeadm reset --force


删除残留文件


rm -f /etc/kubernetes/kubelet.conf

rm -f /etc/kubernetes/bootstrap-kubelet.conf

rm -f /etc/kubernetes/pki/ca.crt


:::


:::note{title="注"}
虚拟重启时，有个工作节点，一直有问题起不来

清理残留文件


sudo rm -f /etc/kubernetes/pki/ca.crt

sudo rm -rf /etc/kubernetes/manifests/

重新执行加入集群命令

kubeadm join 192.168.201.100:6443 --token 3glsa8.8q59hc078gz6382m \
--discovery-token-ca-cert-hash sha256:729e927fa4450c6c84b4912a15e505a4f3204c7ca625913e0e20945e0a5a36d1


命令可以去主节点生成，生成命令：

kubeadm token create --print-join-command
:::
6. 配置集群网络

```js
vi kube-flannel.yml
```


```yaml
---
kind: Namespace
apiVersion: v1
metadata:
  name: kube-flannel
  labels:
    k8s-app: flannel
    pod-security.kubernetes.io/enforce: privileged
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  labels:
    k8s-app: flannel
  name: flannel
rules:
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - nodes/status
  verbs:
  - patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  labels:
    k8s-app: flannel
  name: flannel
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: flannel
subjects:
- kind: ServiceAccount
  name: flannel
  namespace: kube-flannel
---
apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    k8s-app: flannel
  name: flannel
  namespace: kube-flannel
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg
  namespace: kube-flannel
  labels:
    tier: node
    k8s-app: flannel
    app: flannel
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "cniVersion": "0.3.1",
      "plugins": [
        {
          "type": "flannel",
          "delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }
        },
        {
          "type": "portmap",
          "capabilities": {
            "portMappings": true
          }
        }
      ]
    }
  net-conf.json: |
    {
      "Network": "10.244.0.0/16",
      "EnableNFTables": false,
      "Backend": {
        "Type": "vxlan"
      }
    }
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds
  namespace: kube-flannel
  labels:
    tier: node
    app: flannel
    k8s-app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/os
                operator: In
                values:
                - linux
      hostNetwork: true
      priorityClassName: system-node-critical
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni-plugin
        image: ghcr.io/flannel-io/flannel-cni-plugin:v1.7.1-flannel1
        command:
        - cp
        args:
        - -f
        - /flannel
        - /opt/cni/bin/flannel
        volumeMounts:
        - name: cni-plugin
          mountPath: /opt/cni/bin
      - name: install-cni
        image: ghcr.io/flannel-io/flannel:v0.27.2
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: ghcr.io/flannel-io/flannel:v0.27.2
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
            add: ["NET_ADMIN", "NET_RAW"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: EVENT_QUEUE_DEPTH
          value: "5000"
        - name: CONT_WHEN_CACHE_NOT_READY
          value: "false"
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
        - name: xtables-lock
          mountPath: /run/xtables.lock
      volumes:
      - name: run
        hostPath:
          path: /run/flannel
      - name: cni-plugin
        hostPath:
          path: /opt/cni/bin
      - name: cni
        hostPath:
          path: /etc/cni/net.d
      - name: flannel-cfg
        configMap:
          name: kube-flannel-cfg
      - name: xtables-lock
        hostPath:
          path: /run/xtables.lock
          type: FileOrCreate
```

1.配置集群环境

1. 导入表数据先创建好表。

```sql
CREATE TABLE IF NOT EXISTS table1 (
    id VARCHAR(255) NOT NULL COMMENT 'id',
    name VARCHAR(255) NOT NULL COMMENT '名字',
    PRIMARY KEY (id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
```
2.需要开启临时本地导入文件权限和临时设置会话时间

```sql
SET GLOBAL local_infile = 1;
-- 临时设置（当前会话有效）
SET GLOBAL wait_timeout = 86400;  -- 24小时
SET GLOBAL interactive_timeout = 86400;
SET GLOBAL net_read_timeout = 3600;  -- 1小时
SET GLOBAL net_write_timeout = 3600;
```

3. 导入本地txt文件数据

```sql
LOAD DATA LOCAL INFILE 'E:/shuju/6.9.txt'  -- 本地文件路径
INTO TABLE table1             -- 导入的表名
FIELDS TERMINATED BY '----'   -- 表数据的分隔符
LINES TERMINATED BY '\n'      -- 导入后换行
(id, name);

-- 以下是忽略错误行导入
LOAD DATA LOCAL INFILE 'E:/shuju/6.9.txt' 
IGNORE INTO TABLE table1  -- 忽略错误行
FIELDS TERMINATED BY '----' 
LINES TERMINATED BY '\n'
(id, name);
```

4.当存在第三列时，第二列存入qq2字段；否则qq2保持NULL57。COALESCE函数确保phone总取最后一列


```sql
LOAD DATA LOCAL INFILE 'E:/shuju/6.9_part1.txt'
IGNORE INTO TABLE qq
FIELDS TERMINATED BY '----'
LINES TERMINATED BY '\n'
(@col1, @col2, @col3)
SET 
    qq = @col1,
    qq2 = IF(@col3 IS NULL, NULL, @col2),
    phone = COALESCE(@col3, @col2);

```

5.当表里有大量数据时，查询会比较吃力，可以建立索引进行查询。 

```sql
-- 把id字段改为bigint类型，节省存储空间（bigint 比 varchar(20) 更高效
ALTER TABLE id MODIFY id BIGINT NOT NULL;

-- 创建索引设置对应字段
CREATE INDEX 索引名称 ON 表名 (字段) USING BTREE;

-- 如果表中是varchar类型，需要强制遵守该sql写法，不然索引失效
SELECT * FROM 表 WHERE 字段 = '123456789';

```


:::note{title="注意"}
如果是varchar类型这样索引是不生效的：

SELECT * FROM 表 WHERE 字段 = 123456789;

相反如果是bigint类型就可以这样查询，索引是生效的
:::

mysql本地导入txt

## 1.下载openssh-9.5p1.tar.gz包
解压openssh-9.5p1.tar.gz包
```js
tar -zxvf openssh-9.5p1.tar.gz
```
## 2.进入openssh-9.5p1文件目录

```js
cd openssh-9.5p1
```

## 3.执行文件目录下文件

```js
./configure
```
## 4.编译、编译安装

```js
make
```

```js
make install
```
## 5.查看SSH版本是否更新。

```js
ssh -V
```


:::info{title="相关信息"}
解决 OpenSSL library not found 或者 Your OpenSSL headers do not match your library. Check config.log for details.
:::

```js
错误的原因就是找不到libcrypto.so或者该文件版本不对。

解决办法：

ssl一般默认是在/usr/local/下，编译的时候指定一下路径就可以通过了。
CCFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure
```

```js
如果不知道具体路径可以全盘搜索libcrypto.so文件，找到对应版本，在用上述方法解决。
find / -name libcrypto.so*
```