apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63680" uid: ef62fc7d-5de5-4e5a-9ee3-30b1c8e3e06f spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T01:47:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.848µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 1.146865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 1.140454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 1.28968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 1.158279ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 1.374784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:17:37Z" - latency: 1.154463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:16:37Z" - latency: 1.136064ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:15:37Z" - latency: 1.362363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:14:37Z" - latency: 1.071216ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63681" uid: 1509387e-7d7e-484b-aee4-4c2e1b26618a spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:46:37Z" message: 'load-balancer-api-external: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.832001ms message: 'load-balancer-api-external: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 6.366428ms message: 'load-balancer-api-external: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:22:37Z" - latency: 3.773306ms message: 'load-balancer-api-external: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 6.963366ms message: 'load-balancer-api-external: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:21:37Z" - latency: 4.020753ms message: 'load-balancer-api-external: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 5.815383ms message: 'load-balancer-api-external: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:20:37Z" - latency: 3.953899ms message: 'load-balancer-api-external: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 6.983948ms message: 'load-balancer-api-external: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:19:37Z" - latency: 5.188756ms message: 'load-balancer-api-external: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 6.626448ms message: 'load-balancer-api-external: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:18:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63682" uid: cbdb88f7-a666-4f30-b199-f01d59651771 spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:46:37Z" message: 'load-balancer-api-internal: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.887143ms message: 'load-balancer-api-internal: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 6.436014ms message: 'load-balancer-api-internal: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:22:37Z" - latency: 3.78824ms message: 'load-balancer-api-internal: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 6.918967ms message: 'load-balancer-api-internal: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:21:37Z" - latency: 5.329796ms message: 'load-balancer-api-internal: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 5.7813ms message: 'load-balancer-api-internal: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:20:37Z" - latency: 5.024782ms message: 'load-balancer-api-internal: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 6.926687ms message: 'load-balancer-api-internal: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:19:37Z" - latency: 3.149583ms message: 'load-balancer-api-internal: tcp connection to af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 6.682484ms message: 'load-balancer-api-internal: resolved host name af3c4ad5fea7d4aaca157a2596029d2a-78342deb719c594c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:18:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-network-check-target-ip-10-0-130-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63677" uid: 18443105-ef69-41a5-9060-37e55a6495b3 spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:47:37Z" message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.993239ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 2.636015ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 2.121162ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 2.185612ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 2.283884ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 2.126094ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:17:37Z" - latency: 1.897997ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:16:37Z" - latency: 2.502831ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:15:37Z" - latency: 2.207058ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:14:37Z" - latency: 2.721516ms message: 'network-check-target-ip-10-0-130-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-network-check-target-ip-10-0-131-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63678" uid: b84b199f-3a90-4795-bf6a-0368d86aec75 spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:47:37Z" message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.004816ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 2.406224ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 2.651318ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 2.549675ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 2.102812ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 2.722319ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:17:37Z" - latency: 1.965497ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:16:37Z" - latency: 2.694314ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:15:37Z" - latency: 2.815209ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:14:37Z" - latency: 2.590064ms message: 'network-check-target-ip-10-0-131-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-network-check-target-ip-10-0-131-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63675" uid: 49b283b9-0f8f-4539-8a7d-1861d5c8778a spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:47:37Z" message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.303µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 978.694µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 975.803µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 971.032µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 834.591µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 1.311194ms message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:17:37Z" - latency: 914.959µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:16:37Z" - latency: 1.279002ms message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:15:37Z" - latency: 991.317µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:14:37Z" - latency: 974.76µs message: 'network-check-target-ip-10-0-131-80: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:40:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-80-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-80.ec2.internal uid: 6bdafb7e-c888-45fd-bf8f-ad3b0a756b40 resourceVersion: "63679" uid: d5d2f135-b703-4c27-8109-d7d478ff3280 spec: sourcePod: network-check-source-7bc5b6bf85-frfzq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T01:46:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.152034ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:37Z" - latency: 1.802585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:22:37Z" - latency: 1.119904ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:37Z" - latency: 1.803717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:21:37Z" - latency: 1.20007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:37Z" - latency: 1.695354ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:20:37Z" - latency: 785.775µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:19:37Z" - latency: 1.732652ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:19:37Z" - latency: 910.476µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:18:37Z" - latency: 2.141141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:18:37Z" kind: List metadata: resourceVersion: ""