更新找不到服务节点的端点片时出错 [英] Error updating Endpoint Slices for Service Node Not Found
问题描述
我尝试在本地kubernetes集群中设置 gitea .刚开始工作时,我可以访问gitea主页.但是,当我尝试重新启动树莓派时.我的Service
I tried setting up gitea in my local kubernetes cluster. At first it was working I can access the gitea home page. But when I tried to reboot my raspberry pi. I got the below error on my Service
我的pod
没问题.
我想知道为什么每次重启设备时都只会出现此错误.
I'm wondering why I only got this error every time i reboot my device.
这是我的配置
kind: Service
apiVersion: v1
metadata:
name: gitea-service
spec:
type: NodePort
selector:
app: gitea
ports:
- name: gitea-http
port: 3000
targetPort: 3000
nodePort: 30000
- name: gitea-ssh
port: 22
targetPort: 22
nodePort: 30002
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: gitea-deployment
labels:
app: gitea
spec:
replicas: 1
serviceName: gitea-service-headless
selector:
matchLabels:
app: gitea
template:
metadata:
labels:
app: gitea
spec:
containers:
- name: gitea
image: gitea/gitea:1.12.2
ports:
- containerPort: 3000
name: gitea
- containerPort: 22
name: git-ssh
volumeMounts:
- name: pv-data
mountPath: /data
volumes:
- name: pv-data
persistentVolumeClaim:
claimName: gitea-pvc
apiVersion: v1
kind: Service
metadata:
name: gitea-service-headless
labels:
app: gitea-service-headless
spec:
clusterIP: None
ports:
- port: 3000
name: gitea-http
targetPort: 3000
- port: 22
name: gitea-https
targetPort: 22
selector:
app: gitea
推荐答案
我想知道为什么每次重启设备时都只会出现此错误.
I'm wondering why I only got this error every time i reboot my device.
好吧,让我们看一下错误:
Well, lets look at the error:
更新服务dev-ops/gitea-service的端点分片时出错:节点"rpi4-a"被删除.找不到
Error updating Endpoint Slices for Service dev-ops/gitea-service: node "rpi4-a" not found
似乎由于以下原因而触发了错误:node "rpi4-a" not found
.为什么找不到?重新引导时,该节点已关闭,pod暂时无法工作,这是服务抛出错误的时间.节点启动后,pod开始工作,但事件会存在一小时(默认情况下),然后自动将其删除.
It look like the error was triggered because: node "rpi4-a" not found
. Why is it not found?? While rebooting, the node is down, pod is not working for a moment and this is when service throws the error. When the node boots up, pod starts working but the events are present for one hour (by default) before they get automatically deleted.
所以不用担心.您重新启动了节点,因此应该预期会出现一些错误. Kubernetes会尽一切努力使一切正常运行,因此当您在不耗尽节点的情况下触发重新启动时,可能会出现一些错误.
So don't worry about it. You rebooted the node so you should expect some errors to appear. Kubernetes tries as hard as it can to keep everything working, so when you trigger the reboot without draining the node, some errors may appear.
这篇关于更新找不到服务节点的端点片时出错的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!