[ ] After you deploy the chain with trh-sdk deploy command, you can wait for 5 mins until everything is propagated and working fine.
Once you wait 5 mins, you can follow the next steps to check if the chain is working well.
[ ] All pods should be running. (The status of pod should be Running)
Command: kubectl get pods -n <chain-name>
e,g,
ubuntu@ip-172-31-8-20:~$ kubectl get pods -n grass
NAME READY STATUS RESTARTS AGE
external-secrets-5d796f6bb9-xlgj7 1/1 Running 0 41m
external-secrets-cert-controller-6985f9c544-szzqc 1/1 Running 0 41m
external-secrets-webhook-68464864dc-tjzg5 1/1 Running 0 41m
grass-1747126592-thanos-stack-op-batcher-77f767bdc7-s2mwb 1/1 Running 0 30m
grass-1747126592-thanos-stack-op-geth-0 1/1 Running 0 30m
grass-1747126592-thanos-stack-op-node-0 1/1 Running 0 30m
grass-1747126592-thanos-stack-op-proposer-7bddbdb9bf-g45hv 1/1 Running 0 30m
op-bridge-1747126664-69959ff69d-wvmkw 1/1 Running 0 37m
[ ] All ingress have been created.
Please ensure that two ingresses are created - one for the op-geth and another one for op-bridge.
Command: kubectl get ingress -n <chain-name>
buntu@ip-172-31-8-20:~$ kubectl get ingress -n grass
NAME CLASS HOSTS ADDRESS PORTS AGE
grass-1747126592-thanos-stack-op-geth-ingress alb * k8s-opgeth-04047a1dd4-480677180.eu-west-1.elb.amazonaws.com 80 32m
op-bridge-1747126664-ingress alb * k8s-bridge-abc4cc742c-1151410943.eu-west-1.elb.amazonaws.com 80 38m
❗ If you can’t mark the above check boxes even though you wait for 5 mins after the deployment, please follow this trouble shooting guide and try to follow above ones.