apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64525" uid: 370bcc78-9481-432c-ad20-faf2ebb450b5 spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T18:50:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 1.157789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 1.531969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 1.639036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 1.21804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 887.217µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:20:35Z" - latency: 1.154175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:19:35Z" - latency: 1.144645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:18:35Z" - latency: 1.036437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:17:35Z" - latency: 916.278µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:16:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64527" uid: 41b00d21-c2ff-45a5-8e3b-70a898c47683 spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T18:49:35Z" message: 'load-balancer-api-external: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.917483ms message: 'load-balancer-api-external: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 7.494386ms message: 'load-balancer-api-external: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:25:35Z" - latency: 4.43739ms message: 'load-balancer-api-external: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 8.133813ms message: 'load-balancer-api-external: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:24:35Z" - latency: 4.546113ms message: 'load-balancer-api-external: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 8.613469ms message: 'load-balancer-api-external: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:23:35Z" - latency: 4.887159ms message: 'load-balancer-api-external: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 6.732792ms message: 'load-balancer-api-external: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:22:35Z" - latency: 5.946885ms message: 'load-balancer-api-external: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 6.867433ms message: 'load-balancer-api-external: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:21:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64526" uid: 00a80a3a-d196-403c-91c1-7a0d64258c23 spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T18:49:35Z" message: 'load-balancer-api-internal: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.89727ms message: 'load-balancer-api-internal: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 7.547036ms message: 'load-balancer-api-internal: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:25:35Z" - latency: 4.430119ms message: 'load-balancer-api-internal: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 8.233527ms message: 'load-balancer-api-internal: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:24:35Z" - latency: 4.534317ms message: 'load-balancer-api-internal: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 8.648583ms message: 'load-balancer-api-internal: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:23:35Z" - latency: 3.767685ms message: 'load-balancer-api-internal: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 6.790346ms message: 'load-balancer-api-internal: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:22:35Z" - latency: 4.237423ms message: 'load-balancer-api-internal: tcp connection to a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 6.912493ms message: 'load-balancer-api-internal: resolved host name a382e97cffa114c81b4cf796fe9f691a-71535b74f52f2d09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T19:21:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-network-check-target-ip-10-0-128-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64521" uid: f4dde2d8-2fd1-471f-a7d1-93c40e6b0a0a spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T18:50:35Z" message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013029ms message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 1.014989ms message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 1.54618ms message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 1.321651ms message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 1.371196ms message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 977.98µs message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:20:35Z" - latency: 933.264µs message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:19:35Z" - latency: 996.993µs message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:18:35Z" - latency: 933.378µs message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:17:35Z" - latency: 1.51575ms message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:16:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-network-check-target-ip-10-0-128-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64524" uid: 5a4a9fc4-6c98-43c2-9e8f-8c2f2a728769 spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T18:50:35Z" message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.24764ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 2.27203ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 2.141407ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 2.186371ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 2.21274ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 1.884027ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:20:35Z" - latency: 2.563755ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:19:35Z" - latency: 2.229951ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:18:35Z" - latency: 2.150394ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:17:35Z" - latency: 2.002965ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:16:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-network-check-target-ip-10-0-141-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64522" uid: 967a71e1-f37a-4f90-9a4f-4e588dbf4910 spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T18:50:35Z" message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.434864ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 2.383328ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 2.544561ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 2.352079ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 2.205299ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 2.54853ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:20:35Z" - latency: 2.306315ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:19:35Z" - latency: 2.524876ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:18:35Z" - latency: 2.251037ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:17:35Z" - latency: 2.043768ms message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:16:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T18:43:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-111-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-111.ec2.internal uid: d4ba7ef8-b307-474a-a303-17f90aa45a1f resourceVersion: "64523" uid: ca755674-5b46-43f5-9305-9b30b6bdacc9 spec: sourcePod: network-check-source-7d88cb55d8-d65zr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T18:49:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.261µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:25:35Z" - latency: 2.020922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T19:25:35Z" - latency: 896.137µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:24:35Z" - latency: 1.795306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T19:24:35Z" - latency: 1.106195ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:23:35Z" - latency: 2.150071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T19:23:35Z" - latency: 796.473µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:22:35Z" - latency: 2.12843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T19:22:35Z" - latency: 905.642µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T19:21:35Z" - latency: 1.760883ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T19:21:35Z" kind: List metadata: resourceVersion: ""