
用于将MicroK8s dqlite数据库备份到AWS S3的Docker镜像。该镜像包含https://github.com/canonical/go-migrator%E5%B7%A5%E5%85%B7%E4%BB%A5%E5%8F%8A%E5%8F%97microk8s dbctl的https://github.com/ubuntu/microk8s/blob/master/scripts/wrappers/dbctl.py%E5%90%AF%E5%8F%91%E7%9A%84%E5%8C%85%E8%A3%85%E8%84%9A%E6%9C%AC%E3%80%82
linux/amd64linux/arm64/v8linux/arm/v7完整代码示例位于./kubernetes/目录下。
首先,需将配置存储为Secret和ConfigMap。
yaml--- # 包含所有敏感数据的Secret apiVersion: v1 kind: Secret metadata: name: microk8s-backup-aws type: Opaque stringData: AWS_REGION: eu-central-1 # 请修改为实际值 AWS_ACCESS_KEY_ID: XXXXXXXXXXXXXXXXXXXX # 请修改为实际值 AWS_SECRET_ACCESS_KEY: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX # 请修改为实际值 --- # 包含非敏感配置信息的ConfigMap apiVersion: v1 kind: ConfigMap metadata: name: microk8s-backup-config data: BUCKET: my-bucket # 请修改为实际值 KEY: "backup/microk8s/" DEBUG: "false"
接下来,可选择进行一次性备份或定时备份。
要对MicroK8s集群执行一次性备份,只需运行一个Pod即可完成备份。
yamlapiVersion: v1 kind: Pod metadata: name: microk8s-backup spec: restartPolicy: OnFailure securityContext: runAsUser: 1000 runAsGroup: 998 # 可能需要调整以适配kine socket的文件权限 fsGroup: 1000 volumes: - name: kine hostPath: path: /var/snap/microk8s/current/var/kubernetes/backend/kine.sock type: Socket containers: - name: backup image: clowa/microk8s-backup:v0.0.2 imagePullPolicy: Always env: - name: KINE_ENDPOINT value: "/kine.sock" - name: AWS_ACCESS_KEY_ID valueFrom: secretKeyRef: name: microk8s-backup-aws key: AWS_ACCESS_KEY_ID - name: AWS_SECRET_ACCESS_KEY valueFrom: secretKeyRef: name: microk8s-backup-aws key: AWS_SECRET_ACCESS_KEY - name: AWS_REGION valueFrom: secretKeyRef: name: microk8s-backup-aws key: AWS_REGION - name: BUCKET valueFrom: configMapKeyRef: name: microk8s-backup-config key: BUCKET - name: KEY valueFrom: configMapKeyRef: name: microk8s-backup-config key: KEY - name: DEBUG valueFrom: configMapKeyRef: name: microk8s-backup-config key: DEBUG volumeMounts: - name: kine mountPath: /kine.sock securityContext: allowPrivilegeEscalation: false resources: requests: cpu: "20m" memory: "20Mi" limits: cpu: "100m" memory: "64Mi"
若需定时执行备份,可使用Kubernetes的CronJob。
yamlapiVersion: batch/v1 kind: CronJob metadata: name: backup-microk8s spec: schedule: "0 21 * * *" # 根据需要调整调度时间 jobTemplate: spec: template: spec: restartPolicy: OnFailure securityContext: runAsUser: 1000 runAsGroup: 998 fsGroup: 1000 volumes: - name: kine hostPath: path: /var/snap/microk8s/current/var/kubernetes/backend/kine.sock type: Socket containers: - name: backup image: clowa/microk8s-backup:v0.0.2 imagePullPolicy: Always securityContext: allowPrivilegeEscalation: false volumeMounts: - name: kine mountPath: /kine.sock env: - name: KINE_ENDPOINT value: "/kine.sock" - name: AWS_ACCESS_KEY_ID valueFrom: secretKeyRef: name: microk8s-backup-aws key: AWS_ACCESS_KEY_ID - name: AWS_SECRET_ACCESS_KEY valueFrom: secretKeyRef: name: microk8s-backup-aws key: AWS_SECRET_ACCESS_KEY - name: AWS_REGION valueFrom: secretKeyRef: name: microk8s-backup-aws key: AWS_REGION - name: BUCKET valueFrom: configMapKeyRef: name: microk8s-backup-config key: BUCKET - name: KEY valueFrom: configMapKeyRef: name: microk8s-backup-config key: KEY - name: DEBUG valueFrom: configMapKeyRef: name: microk8s-backup-config key: DEBUG resources: requests: cpu: "20m" memory: "20Mi" limits: cpu: "100m" memory: "64Mi"
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。





探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务