Kubernetes Weblogic操作员安装失败
我正在尝试将Kubernetes运算符安装在VM主机上,该主机已启动为主节点,并在两个不同的VM中具有两个Worker节点。
我以前已经成功安装了操作员,并且在域上的升级期间陷入困境之前,它运行得很完美,我必须清理所有内容,然后再次安装整个Kubernetes和Kubernetes Weblogic操作员。但是目前,我有一些问题无法弄清楚该解决方案,因为我不是这项技术的专家。 (也许我还没有删除应进行清理的内容)
首先,因为我清理了我所知道的所有内容与Kubernetes相关并在值得信赖的教程之后再次安装了它,所以我设法达到了点我必须在哪里启动集群。
kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket unix:///var/run/cri-dockerd.sock --ignore-preflight-errors=all
使用法兰绒的法牌网络之后,我想使用
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
我使用此命令发起并使用了此特定的IP,因为在成功部署了
。在我启动并成功加入了其他两个工人节点之后,我到达了这个位置:
NAME STATUS ROLES AGE VERSION
master-node Ready control-plane 43h v1.24.0
worker-node1 Ready <none> 43h v1.24.1
worker-node2 Ready <none> 43h v1.24.1
在一切准备就绪之后(或者那是我想)之后,我需要在Oracle的正式文档后开始安装Kubernetes Weblogic操作员。 启动。
了快速
我使用 图像并将它们放在VM中的Docker中,并安装Helm Kubernetes软件包管理器,请使用以下方式安装操作员:
helm install sample-weblogic-operator kubernetes/charts/weblogic-operator \
--namespace sample-weblogic-operator-ns \
--set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.4.0 \
--set serviceAccount=sample-weblogic-operator-sa \
--set "enableClusterRoleBinding=true" \
--set "domainNamespaceSelectionStrategy=LabelSelector" \
--set "domainNamespaceLabelSelector=weblogic-operator\=enabled" \
要注意所有命名空间和服务已经设置。
在这一点上,这是凌乱的地方。操作员永远不会启动,并且会有以下错误:
如果我得到豆荚
sample-weblogic-operator-ns weblogic-operator-85667bfb6f-fdcw6 0/1 CrashLoopBackOff 406 (3m22s ago) 22h
,并且在Pod的描述中,
Warning Unhealthy 20m (x1077 over 22h) kubelet Liveness probe failed:
Warning BackOff 5m12s (x4906 over 22h) kubelet Back-off restarting failed container
Warning Unhealthy 6s (x2424 over 23h) kubelet Readiness probe failed:
所有这些都是运行的POD:
接下来,我尝试查看操作员的日志获取多个具有相同特征的错误:
"message":"Exception thrown","exception":"\nio.kubernetes.client.openapi.ApiException: java.net.NoRouteToHostException: No route to host
经过一番挖掘,我开始认为这是由于某些网络构造的配置错误,并开始研究日志的其他豆荚,我发现了以下内容:
在Coredns Pod中进行
[INFO] plugin/ready: Still waiting on: "kubernetes"
在研究之后,此时 了研究。发现这必须与主机和IP一起做一些事情,但这是我迷路的同时。接下来我可以尝试什么?
I am trying to install the Kubernetes Operator on a VM host which has been initiated as the master node and has two worker nodes in two different VMs.
I had successfully installed the Operator before and it was running perfectly, before something was stuck during the upgrade of a domain and I had to clean everything up and re-install the whole Kubernetes and Kubernetes Weblogic Operator again. But at this time I have some issues that I am not able to figure out the solution as I am not an expert on this tech. (Maybe I have not deleted something that should be for the cleanup)
First, as I have cleaned up everything that I was aware of that was connected with the Kubernetes and re-installed it again following a trusted tutorial, I managed to reach the point where I had to initiate the cluster.
kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket unix:///var/run/cri-dockerd.sock --ignore-preflight-errors=all
I initiated with this command and used this specific ip because I wanted to use after that the Flannel Networking using
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
Flannel is deployed successfully.
After I initiated and successfully joined the other two worker nodes I got to this position:
NAME STATUS ROLES AGE VERSION
master-node Ready control-plane 43h v1.24.0
worker-node1 Ready <none> 43h v1.24.1
worker-node2 Ready <none> 43h v1.24.1
After everything is ready (or that was what I thought) I need to start installing the Kubernetes Weblogic Operator following the official documentation of Oracle. I used the Quick Start.*
Quick Start from Oracle Documentation
After pulling all images and have them in the docker in the VM, and also installing the helm Kubernetes package manager I proceed to the installation of the Operator using:
helm install sample-weblogic-operator kubernetes/charts/weblogic-operator \
--namespace sample-weblogic-operator-ns \
--set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.4.0 \
--set serviceAccount=sample-weblogic-operator-sa \
--set "enableClusterRoleBinding=true" \
--set "domainNamespaceSelectionStrategy=LabelSelector" \
--set "domainNamespaceLabelSelector=weblogic-operator\=enabled" \
To be noted that all namespaces and services have been set up.
At this point this is where it gets messy. The operator never starts and has the following errors:
If I get the pods
sample-weblogic-operator-ns weblogic-operator-85667bfb6f-fdcw6 0/1 CrashLoopBackOff 406 (3m22s ago) 22h
And in the describe of the pod
Warning Unhealthy 20m (x1077 over 22h) kubelet Liveness probe failed:
Warning BackOff 5m12s (x4906 over 22h) kubelet Back-off restarting failed container
Warning Unhealthy 6s (x2424 over 23h) kubelet Readiness probe failed:
These are all the pods running:
Next, I tried to see the logs of the Operator and I get multiple errors which all have the same characteristic:
"message":"Exception thrown","exception":"\nio.kubernetes.client.openapi.ApiException: java.net.NoRouteToHostException: No route to host
After some digging I started to think that this was due to some networking misconfiguration and started to look into the other pods for logs and I found the following:
In coredns pod
[INFO] plugin/ready: Still waiting on: "kubernetes"
At this point after research I found out that this has to do something with the hosts and the IP, but it is the same point where I got lost. What can I try next?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
至少,防火墙阻止了该过程。我不知道这些设置,也没有对此的实际知识。经过大量的搜索和尝试,找到了它。
我启用了法兰绒IPS,然后效果很好。
At least, the firewall was blocking the process. I was not aware of those settings and didn't have the actual knowledge on that. Found it after a lot of searching and trying.
I have enabled the IPs of flannel and then it worked fine.