Solved

Cloud Clustering 22R2

  • 11 December 2023
  • 3 replies
  • 56 views
S
Rank
Userlevel 3
Badge +8

Dear Experts ,

We are setting up the IFS Cloud 22R2 cluster environment and after joining the node we are running this script “ .\main.ps1 -resource 'INGRESS' “ but while checking the status we seen the status of ifs-ingrass as PodInitializing  ,, below is the image of status ..can we go head with next steps or we are missing something which need to correct. 

 

Please suggest. 

 

ifs-ingress      linkerd-proxy-injector-56697c4759-qhg5t                 0/2     PodInitializing   0                174m    10.1.126.6      gmuvdifs-coe-04   <none>           <none>
ifs-ingress      linkerd-destination-5f7c775c57-drpdf                    0/4     PodInitializing   0                174m    10.1.14.69      gmuvdifs-coe-05   <none>           <none>

icon

Best answer by Sujeet Saxena 30 January 2024, 11:16

View original

3 replies

Charith Epitawatta
Rank
Userlevel 7
Badge +31

Hi @Sujeet Saxena,

Since all requests come to the cluster through Ingress, it is important to make sure the Ingress is working correctly before proceeding to the next step. Therefore please make sure why the Pods are stuck in this state first. 

Normally a Pod gets stuck in this state when the Init containers within the Pod have not completed successfully. Please run the following commands to see why.

  • kubectl describe <PodName> -n ifs-ingress
  • kubectl logs <PodName> -c <InitContainerName> -n ifs-ingress

For the second command, you can find the Init Container name from the output of the first command. It should be under the “Init Containers” section. 

Hope this helps!

Charith - https://charith.xyz
S
Rank
Userlevel 3
Badge +8

Thanks for the reply , i am getting below log  message while running the command to check the logs..any help would be appreciated.

 

PS D:\IFSBuild_home\IFS22_2_7_Buildhome\build-home\ifsinstaller> kubectl logs linkerd-destination-764f947c85-gd8rn -c linkerd-init -n ifs-ingress
2023/12/12 10:19:34 Tracing this script execution as [1702376374]
2023/12/12 10:19:34 current state
------------------------------------------------------------
2023/12/12 10:19:34 :; iptables-save
2023/12/12 10:19:34

 

2023/12/12 10:19:34 configuration
------------------------------------------------------------
2023/12/12 10:19:34 Will ignore port [4190 4191 4567 4568] on chain PROXY_INIT_REDIRECT
2023/12/12 10:19:34 Will redirect all INPUT ports to proxy
2023/12/12 10:19:34 Ignoring uid 2102
2023/12/12 10:19:34 Will ignore port [443] on chain PROXY_INIT_OUTPUT
2023/12/12 10:19:34 Redirecting all OUTPUT to 4140
2023/12/12 10:19:34

 

2023/12/12 10:19:34 adding rules
------------------------------------------------------------
2023/12/12 10:19:34 :; iptables -t nat -N PROXY_INIT_REDIRECT -m comment --comment proxy-init/redirect-common-chain/1702376374
2023/12/12 10:19:34 :; iptables -t nat -A PROXY_INIT_REDIRECT -p tcp --match multiport --dports 4190,4191,4567,4568 -j RETURN -m comment --comment proxy-init/ignore-port-4190,4191,4567,4568/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A PROXY_INIT_REDIRECT -p tcp -j REDIRECT --to-port 4143 -m comment --comment proxy-init/redirect-all-incoming-to-proxy-port/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A PREROUTING -j PROXY_INIT_REDIRECT -m comment --comment proxy-init/install-proxy-init-prerouting/1702376374
2023/12/12 10:19:35 :; iptables -t nat -N PROXY_INIT_OUTPUT -m comment --comment proxy-init/redirect-common-chain/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A PROXY_INIT_OUTPUT -m owner --uid-owner 2102 -j RETURN -m comment --comment proxy-init/ignore-proxy-user-id/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A PROXY_INIT_OUTPUT -o lo -j RETURN -m comment --comment proxy-init/ignore-loopback/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A PROXY_INIT_OUTPUT -p tcp --match multiport --dports 443 -j RETURN -m comment --comment proxy-init/ignore-port-443/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A PROXY_INIT_OUTPUT -p tcp -j REDIRECT --to-port 4140 -m comment --comment proxy-init/redirect-all-outgoing-to-proxy-port/1702376374
2023/12/12 10:19:35 :; iptables -t nat -A OUTPUT -j PROXY_INIT_OUTPUT -m comment --comment proxy-init/install-proxy-init-output/1702376374
2023/12/12 10:19:35

 

2023/12/12 10:19:35 end state
------------------------------------------------------------
2023/12/12 10:19:35 :; iptables-save
2023/12/12 10:19:35 # Generated by iptables-save v1.8.7 on Tue Dec 12 10:19:35 2023
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:PROXY_INIT_OUTPUT - [0:0]
:PROXY_INIT_REDIRECT - [0:0]
-A PREROUTING -m comment --comment "proxy-init/install-proxy-init-prerouting/1702376374" -j PROXY_INIT_REDIRECT
-A OUTPUT -m comment --comment "proxy-init/install-proxy-init-output/1702376374" -j PROXY_INIT_OUTPUT
-A PROXY_INIT_OUTPUT -m owner --uid-owner 2102 -m comment --comment "proxy-init/ignore-proxy-user-id/1702376374" -j RETURN
-A PROXY_INIT_OUTPUT -o lo -m comment --comment "proxy-init/ignore-loopback/1702376374" -j RETURN
-A PROXY_INIT_OUTPUT -p tcp -m multiport --dports 443 -m comment --comment "proxy-init/ignore-port-443/1702376374" -j RETURN
-A PROXY_INIT_OUTPUT -p tcp -m comment --comment "proxy-init/redirect-all-outgoing-to-proxy-port/1702376374" -j REDIRECT --to-ports 4140
-A PROXY_INIT_REDIRECT -p tcp -m multiport --dports 4190,4191,4567,4568 -m comment --comment "proxy-init/ignore-port-4190,4191,4567,4568/1702376374" -j RETURN
-A PROXY_INIT_REDIRECT -p tcp -m comment --comment "proxy-init/redirect-all-incoming-to-proxy-port/1702376374" -j REDIRECT --to-ports 4143
COMMIT
# Completed on Tue Dec 12 10:19:35 2023

 

2023/12/12 10:19:35

S
Rank
Userlevel 3
Badge +8

This is resolved after restart the VM, its seems proper resources were not allocated and which got resolved after restart the VM..

 

Thanks all for your help.

Reply


Terms & ConditionsCookie settings