-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
None
We have installed 1.28 k8s on top of that we deployed RIC but not able to install RIC pod as v1beta1 API version got deprecated in latest k8s ,so we replaced v1beta1 with v1 now able to deploy all RIC pods but kong pod is in crash loopback due to Ingress controller container is not coming it got stuck in 1/2 state.
Snip for kong pod:-
ricplt r4-infrastructure-kong-7d766b49bb-n89fs 1/2 CrashLoopBackOff 8 (2m26s ago) 16m
kubectl get pod r4-infrastructure-kong-7d766b49bb-7hvzt -n ricplt -o yaml | grep -i container
containers:
- containerPort: 8444
- containerPort: 32080
- containerPort: 32443
- containerPort: 9542
message: 'containers with unready status: [ingress-controller]'
reason: ContainersNotReady
message: 'containers with unready status: [ingress-controller]'
reason: ContainersNotReady
type: ContainersReady
containerStatuses: - containerID: containerd://1cc469bccbee3b862b3be875ec7713a5706561a322b695021127b41cfb501a39
containerID: containerd://1cc469bccbee3b862b3be875ec7713a5706561a322b695021127b41cfb501a39
message: back-off 5m0s restarting failed container=ingress-controller pod=r4-infrastructure-kong-7d766b49bb-7hvzt_ricplt(032be22f-8d25-4ba3-8c63-ce337b40fa9b) - containerID: containerd://9226dafe7a7de0f3214b9ec359c39ec65c48ac68a1d80e65987280f6b15c7ed0
root@kubernetes-master:~/ric-dep/helm/infrastructure#
After that we have changed v1beta to v1 version ,