PostgreSQL角色不存在错误解决方案 Anonymous 发布于 2023-07-25 收录于 数据库 运维PostgreSQL “role does not exist” 错误解决方案 问题描述 在迁移或恢复Grafana数据库时,常见的错误之一是遇到类似以下的错误信息:
PostgreSQL角色错误排查与解决方案 Anonymous 发布于 2023-07-25 收录于 数据库 运维PostgreSQL角色错误排查与解决方案 在云原生环境中使用PostgreSQL数据库时,角色(Role)相关的错误是常见的问题之一。本文将详细介绍PostgreSQL角色错误的原因、排查方法和解决方案,特别是在Grafana等应用迁移场景中的处理方法。
Istio全局配置 kbsonlong 发布于 2023-07-17 收录于 云原生全局关闭重试 istio默认重试2次1 2 3 4 5 6 7 8 9 apiVersion: v1 data: mesh: |- ... ... defaultHttpRetryPolicy: attempts: 0 ... ...
01-利用vscode与kind搭建kubernetes开发环境 kbsonlong 发布于 2023-07-07 收录于 Kubernetes本文基于1.27.0版本Kind 创建集群 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 cat << EOF > dev.yaml kind: Cluster apiVersion: "kind.x-k8s.io/v1alpha4" kubeadmConfigPatches: - | apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration metadata: name: dev imageRepository: registry.aliyuncs.com/google_containers networking: podSubnet: "10.8.0.0/16" serviceSubnet: "10.9.0.0/16" nodes: - role: control-plane image: kindest/node:v1.27.0@sha256:c6b22e613523b1af67d4bc8a0c38a4c3ea3a2b8fbc5b367ae36345c9cb844518 extraPortMappings: - containerPort: 2379 hostPort: 2379 protocol: TCP EOF kind create cluster --name dev --config=dev.yaml
Karmada快速体验 kbsonlong 发布于 2023-06-30 收录于 Karmada 云原生环境准备 利用 kind 快速创建 kubernetes 集群环境1 LOCAL_IP=172.25.163.181创建控制面集群 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 cat << EOF > controler.yaml kind: Cluster apiVersion: "kind.x-k8s.io/v1alpha4" kubeadmConfigPatches: - | apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration metadata: name: controler imageRepository: registry.aliyuncs.com/google_containers networking: apiServerAddress: ${LOCAL_IP} podSubnet: "10.8.0.0/16" serviceSubnet: "10.9.0.0/16" nodes: - role: control-plane image: kindest/node:v1.21.1@sha256:69860bda5563ac81e3c0057d654b5253219618a22ec3a346306239bba8cfa1a6 extraPortMappings: - containerPort: 5443 hostPort: 5443 protocol: TCP EOF kind create cluster --name controler --config=controler.yaml创建成员(member1)集群 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 cat << EOF > member1.yaml kind: Cluster apiVersion: "kind.x-k8s.io/v1alpha4" kubeadmConfigPatches: - | apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration metadata: name: member1 imageRepository: registry.aliyuncs.com/google_containers networking: apiServerAddress: ${LOCAL_IP} podSubnet: "10.10.0.0/16" serviceSubnet: "10.11.0.0/16" nodes: - role: control-plane image: kindest/node:v1.20.15@sha256:a32bf55309294120616886b5338f95dd98a2f7231519c7dedcec32ba29699394 EOF kind create cluster --name member1 --config=member1.yaml创建成员(member2)集群 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 cat << EOF > member2.yaml kind: Cluster apiVersion: "kind.x-k8s.io/v1alpha4" kubeadmConfigPatches: - | apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration metadata: name: member2 imageRepository: registry.aliyuncs.com/google_containers networking: apiServerAddress: ${LOCAL_IP} podSubnet: "10.12.0.0/16" serviceSubnet: "10.13.0.0/16" nodes: - role: control-plane image: kindest/node:v1.20.15@sha256:a32bf55309294120616886b5338f95dd98a2f7231519c7dedcec32ba29699394 EOF kind create cluster --name member2 --config=member2.yaml获取集群kubeconfig 1 2 kind get kubeconfig --name=member1 > member1.conf kind get kubeconfig --name=member2 > member2.conf
防止已取消接管的命名空间在集群离线时被驱逐删除 kbsonlong 发布于 2023-06-29 收录于 Karmada概述 当 Karmada 中的 ClusterPropagationPolicy 被删除或修改以取消对命名空间的资源接管后,成员集群上可能仍然存在相关的 Karmada 注解和标签。在成员集群离线时,这些命名空间可能会被 Karmada 的驱逐机制误删除。本文档提供了多种解决方案来防止这种情况发生。