apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "46683" uid: 965ae5c8-12ae-4d54-a681-361b467a6141 spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T22:08:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.451µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 1.014674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 1.471437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 819.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:26:52Z" - latency: 919.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:25:52Z" - latency: 1.062318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:24:52Z" - latency: 941.459µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:23:52Z" - latency: 926.26µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:22:52Z" - latency: 869.212µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:21:52Z" - latency: 983.086µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:20:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "49250" uid: f1cafc2c-44f5-4d8c-9486-1f56951daabd spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T22:07:52Z" message: 'load-balancer-api-external: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.196312ms message: 'load-balancer-api-external: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:31:52Z" - latency: 7.344769ms message: 'load-balancer-api-external: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:31:52Z" - latency: 5.486707ms message: 'load-balancer-api-external: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:30:52Z" - latency: 7.065411ms message: 'load-balancer-api-external: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:30:52Z" - latency: 3.990723ms message: 'load-balancer-api-external: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 6.614744ms message: 'load-balancer-api-external: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:29:52Z" - latency: 3.981678ms message: 'load-balancer-api-external: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 8.473146ms message: 'load-balancer-api-external: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:28:52Z" - latency: 4.984178ms message: 'load-balancer-api-external: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 7.752679ms message: 'load-balancer-api-external: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:27:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "49251" uid: ac125dcc-efa7-49a8-a29d-3b5f41832626 spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T22:07:52Z" message: 'load-balancer-api-internal: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.217605ms message: 'load-balancer-api-internal: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:31:52Z" - latency: 7.352731ms message: 'load-balancer-api-internal: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:31:52Z" - latency: 5.400716ms message: 'load-balancer-api-internal: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:30:52Z" - latency: 7.022294ms message: 'load-balancer-api-internal: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:30:52Z" - latency: 3.975624ms message: 'load-balancer-api-internal: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 6.661026ms message: 'load-balancer-api-internal: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:29:52Z" - latency: 3.988531ms message: 'load-balancer-api-internal: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 8.361163ms message: 'load-balancer-api-internal: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:28:52Z" - latency: 4.33088ms message: 'load-balancer-api-internal: tcp connection to a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 7.690295ms message: 'load-balancer-api-internal: resolved host name a6d22e8db8a854cb4800dca9a8c9aa5d-a9e0b15ef07635da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T22:27:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-ip-10-0-128-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "46682" uid: 80a3c8e5-0a5d-485a-a486-b2a8da73b261 spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T22:08:52Z" message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.187769ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 2.269197ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 2.791935ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 2.279981ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:26:52Z" - latency: 2.481034ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:25:52Z" - latency: 2.286109ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:24:52Z" - latency: 2.431391ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:23:52Z" - latency: 2.569089ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:22:52Z" - latency: 2.408555ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:21:52Z" - latency: 2.388905ms message: 'network-check-target-ip-10-0-128-35: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:20:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-ip-10-0-130-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "46681" uid: 3402376c-998e-4de4-9510-0ca9fafb9143 spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T22:08:52Z" message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.166215ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 2.813501ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 2.837164ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 2.923504ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:26:52Z" - latency: 2.416052ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:25:52Z" - latency: 2.510633ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:24:52Z" - latency: 2.449017ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:23:52Z" - latency: 2.198039ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:22:52Z" - latency: 2.22882ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:21:52Z" - latency: 2.328345ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:20:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-ip-10-0-132-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "46680" uid: ddddd39b-27df-461c-8cad-d83295d123b7 spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T22:08:52Z" message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002324ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 862.127µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 1.522153ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 1.019827ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:26:52Z" - latency: 942.688µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:25:52Z" - latency: 828.965µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:24:52Z" - latency: 895.404µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:23:52Z" - latency: 1.335905ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:22:52Z" - latency: 1.481323ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:21:52Z" - latency: 920.73µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:20:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T22:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.ec2.internal uid: c0ec445c-3e0a-4288-94c8-47be0391f359 resourceVersion: "49249" uid: 9010a37a-cb03-41ea-96c2-140054565ab5 spec: sourcePod: network-check-source-989f8b8dc-rrm5w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T22:07:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.076613ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:31:52Z" - latency: 2.11205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T22:31:52Z" - latency: 758.913µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:30:52Z" - latency: 1.666071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T22:30:52Z" - latency: 856.457µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:29:52Z" - latency: 1.811993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T22:29:52Z" - latency: 901.241µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:28:52Z" - latency: 1.986019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T22:28:52Z" - latency: 1.155099ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T22:27:52Z" - latency: 2.206721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T22:27:52Z" kind: List metadata: resourceVersion: ""