apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "23188" uid: 97dd4456-b176-47f9-91da-f7d55fca188c spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T17:25:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 991.911µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 1.161387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:17Z" - latency: 894.901µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:17Z" - latency: 966.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:17Z" - latency: 963.871µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:17Z" - latency: 876.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:17Z" - latency: 950.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:17Z" - latency: 899.451µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:17Z" - latency: 1.091114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "24705" uid: c01078b3-f334-4624-a86a-a69c0a7702c5 spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:24:17Z" message: 'load-balancer-api-external: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.870026ms message: 'load-balancer-api-external: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:42:17Z" - latency: 10.856492ms message: 'load-balancer-api-external: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:42:17Z" - latency: 6.124638ms message: 'load-balancer-api-external: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:41:17Z" - latency: 15.98761ms message: 'load-balancer-api-external: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:41:17Z" - latency: 5.162339ms message: 'load-balancer-api-external: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:40:17Z" - latency: 9.618958ms message: 'load-balancer-api-external: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:40:17Z" - latency: 5.242662ms message: 'load-balancer-api-external: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 10.435462ms message: 'load-balancer-api-external: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:39:17Z" - latency: 4.162665ms message: 'load-balancer-api-external: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 9.96678ms message: 'load-balancer-api-external: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:38:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "24706" uid: b2e49a9a-d298-4a3b-8284-c78656f73f85 spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:24:17Z" message: 'load-balancer-api-internal: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.914861ms message: 'load-balancer-api-internal: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:42:17Z" - latency: 11.850732ms message: 'load-balancer-api-internal: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:42:17Z" - latency: 5.226239ms message: 'load-balancer-api-internal: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:41:17Z" - latency: 15.964751ms message: 'load-balancer-api-internal: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:41:17Z" - latency: 5.198154ms message: 'load-balancer-api-internal: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:40:17Z" - latency: 9.568291ms message: 'load-balancer-api-internal: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:40:17Z" - latency: 6.433328ms message: 'load-balancer-api-internal: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 10.378868ms message: 'load-balancer-api-internal: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:39:17Z" - latency: 4.281877ms message: 'load-balancer-api-internal: tcp connection to a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 10.22046ms message: 'load-balancer-api-internal: resolved host name a9a4b9d8af0eb44baa5a1d882de72b72-31ac8b929feaa8df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:38:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-ip-10-0-131-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "23186" uid: 0bee9c2e-da4d-463e-8be0-56ad8be62383 spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:25:17Z" message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.491614ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 2.457962ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 2.415336ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:17Z" - latency: 2.326532ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:17Z" - latency: 2.436583ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:17Z" - latency: 2.497499ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:17Z" - latency: 2.391995ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:17Z" - latency: 2.490952ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:17Z" - latency: 2.491472ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:17Z" - latency: 2.380778ms message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-ip-10-0-136-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "23185" uid: 72289576-bae7-4f3d-a4ae-e70fdb744971 spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:25:17Z" message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.34407ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 901.286µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 816.687µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:17Z" - latency: 824.773µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:17Z" - latency: 1.431789ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:17Z" - latency: 891.405µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:17Z" - latency: 1.386005ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:17Z" - latency: 960.867µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:17Z" - latency: 1.326839ms message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:17Z" - latency: 913.993µs message: 'network-check-target-ip-10-0-136-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-ip-10-0-142-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "23187" uid: 48765bb6-9176-4cc1-8a3b-28ea74c7d14a spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:25:17Z" message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.902811ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 2.298124ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 2.181289ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:37:17Z" - latency: 1.968452ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:36:17Z" - latency: 2.338925ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:35:17Z" - latency: 2.20503ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:34:17Z" - latency: 2.229659ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:33:17Z" - latency: 2.437725ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:32:17Z" - latency: 2.242257ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:31:17Z" - latency: 1.992086ms message: 'network-check-target-ip-10-0-142-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:30:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-107-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-107.ec2.internal uid: d09056db-6ff0-4e4f-97ff-80885ba61b95 resourceVersion: "24704" uid: e97d847a-fefe-40e1-9f03-aad4379b80a2 spec: sourcePod: network-check-source-65bdbbff45-9wrgf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T17:24:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.461844ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:42:17Z" - latency: 2.874083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:42:17Z" - latency: 744.294µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:41:17Z" - latency: 2.331587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:41:17Z" - latency: 948.141µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:40:17Z" - latency: 1.710016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:40:17Z" - latency: 810.89µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:39:17Z" - latency: 1.74324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:39:17Z" - latency: 892.183µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:38:17Z" - latency: 1.845307ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:38:17Z" kind: List metadata: resourceVersion: ""