apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "45065" uid: 5f4533d5-bc42-4911-bc23-42dfeedd9e2f spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T12:22:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.064914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 1.121014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 1.133454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 1.195827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:53Z" - latency: 1.122454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:53Z" - latency: 957.05µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:53Z" - latency: 1.150719ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:53Z" - latency: 901.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:53Z" - latency: 1.273694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:53Z" - latency: 1.347468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "47111" uid: 20354d05-cd45-4cef-9a7f-f009f93912d2 spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:21:53Z" message: 'load-balancer-api-external: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.247682ms message: 'load-balancer-api-external: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:45:53Z" - latency: 6.445059ms message: 'load-balancer-api-external: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:45:53Z" - latency: 4.97247ms message: 'load-balancer-api-external: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:44:53Z" - latency: 6.216699ms message: 'load-balancer-api-external: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:44:53Z" - latency: 4.580538ms message: 'load-balancer-api-external: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 14.924959ms message: 'load-balancer-api-external: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:43:53Z" - latency: 4.48109ms message: 'load-balancer-api-external: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 7.358115ms message: 'load-balancer-api-external: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:42:53Z" - latency: 4.283197ms message: 'load-balancer-api-external: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 7.188563ms message: 'load-balancer-api-external: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "47112" uid: 3c1126df-b11c-4bec-8a21-f0d02f2dc95f spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:21:53Z" message: 'load-balancer-api-internal: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.116815ms message: 'load-balancer-api-internal: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:45:53Z" - latency: 6.519582ms message: 'load-balancer-api-internal: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:45:53Z" - latency: 3.861626ms message: 'load-balancer-api-internal: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:44:53Z" - latency: 6.409007ms message: 'load-balancer-api-internal: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:44:53Z" - latency: 4.935187ms message: 'load-balancer-api-internal: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 15.035247ms message: 'load-balancer-api-internal: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:43:53Z" - latency: 3.547705ms message: 'load-balancer-api-internal: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 7.455801ms message: 'load-balancer-api-internal: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:42:53Z" - latency: 4.243367ms message: 'load-balancer-api-internal: tcp connection to a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 7.250667ms message: 'load-balancer-api-internal: resolved host name a9cb9d09d40b84a2480f56a921560269-513a8f1f0c060387.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-network-check-target-ip-10-0-136-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "45063" uid: 41015dae-b534-49a8-8fd8-ab1104b71d74 spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:22:53Z" message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.112407ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 2.328721ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 2.187331ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 2.308978ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:53Z" - latency: 2.363997ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:53Z" - latency: 2.198834ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:53Z" - latency: 2.136786ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:53Z" - latency: 2.084677ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:53Z" - latency: 2.129517ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:53Z" - latency: 2.619516ms message: 'network-check-target-ip-10-0-136-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-network-check-target-ip-10-0-137-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "45064" uid: 5e729d01-507e-4350-a5e5-2aef1203ffc1 spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:22:53Z" message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.344331ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 2.200268ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 2.674703ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 2.207441ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:53Z" - latency: 2.146702ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:53Z" - latency: 2.821188ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:53Z" - latency: 2.326208ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:53Z" - latency: 2.351181ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:53Z" - latency: 2.116141ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:53Z" - latency: 2.193336ms message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-network-check-target-ip-10-0-139-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "45061" uid: 9cf262e3-1c5a-455e-aa44-7ce7769ae697 spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:22:53Z" message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007186ms message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 896.735µs message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 1.52958ms message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 859.126µs message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:53Z" - latency: 1.269387ms message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:53Z" - latency: 880.172µs message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:53Z" - latency: 1.274527ms message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:53Z" - latency: 971.847µs message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:53Z" - latency: 1.240615ms message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:53Z" - latency: 1.011075ms message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-21-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-21.ec2.internal uid: 73e818a2-04c2-4d87-a173-9a75f2b74d9a resourceVersion: "47110" uid: 86114380-2060-41e3-a030-808b032a1da8 spec: sourcePod: network-check-source-dbd9cf844-l85xl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T12:21:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016991ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:45:53Z" - latency: 1.883732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:45:53Z" - latency: 913.135µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:44:53Z" - latency: 1.568171ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:44:53Z" - latency: 1.152215ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:43:53Z" - latency: 2.051434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:43:53Z" - latency: 865.555µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:42:53Z" - latency: 1.738708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:42:53Z" - latency: 983.421µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:41:53Z" - latency: 1.665546ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:41:53Z" kind: List metadata: resourceVersion: ""