apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "33230" uid: ce194d73-3d50-4e8a-973a-c41979c1108a spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:10:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:12Z" - latency: 1.130117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:12Z" - latency: 1.17304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:12Z" - latency: 984.451µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:12Z" - latency: 1.352867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:12Z" - latency: 1.124775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:12Z" - latency: 1.012572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:12Z" - latency: 1.123919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:12Z" - latency: 1.05631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:12Z" - latency: 1.135027ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "35685" uid: e3fe9e99-97c9-4619-b2fe-7d06626adc2b spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:09:12Z" message: 'load-balancer-api-external: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.149127ms message: 'load-balancer-api-external: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:12Z" - latency: 9.03847ms message: 'load-balancer-api-external: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:51:12Z" - latency: 3.905709ms message: 'load-balancer-api-external: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:12Z" - latency: 8.722302ms message: 'load-balancer-api-external: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:50:12Z" - latency: 4.557083ms message: 'load-balancer-api-external: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:49:12Z" - latency: 7.846056ms message: 'load-balancer-api-external: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:49:12Z" - latency: 7.928313ms message: 'load-balancer-api-external: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:12Z" - latency: 8.701841ms message: 'load-balancer-api-external: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:48:12Z" - latency: 4.979546ms message: 'load-balancer-api-external: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:12Z" - latency: 8.351281ms message: 'load-balancer-api-external: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:47:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "35684" uid: 602d6b46-6b24-4047-bdd7-5ab588ec1c5d spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:09:12Z" message: 'load-balancer-api-internal: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.145203ms message: 'load-balancer-api-internal: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:12Z" - latency: 8.965202ms message: 'load-balancer-api-internal: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:51:12Z" - latency: 4.014416ms message: 'load-balancer-api-internal: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:12Z" - latency: 8.627327ms message: 'load-balancer-api-internal: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:50:12Z" - latency: 4.526009ms message: 'load-balancer-api-internal: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:49:12Z" - latency: 7.809781ms message: 'load-balancer-api-internal: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:49:12Z" - latency: 8.764331ms message: 'load-balancer-api-internal: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:12Z" - latency: 8.616139ms message: 'load-balancer-api-internal: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:48:12Z" - latency: 6.184562ms message: 'load-balancer-api-internal: tcp connection to acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:12Z" - latency: 8.276321ms message: 'load-balancer-api-internal: resolved host name acda72442a211433ea8f6ae21bdb85ca-01657143bc033186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:47:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-network-check-target-ip-10-0-128-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "33226" uid: c746839c-c8db-4f6e-84db-019850bb68a1 spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:10:12Z" message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.114608ms message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:12Z" - latency: 1.020282ms message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:12Z" - latency: 862.778µs message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:12Z" - latency: 910.853µs message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:12Z" - latency: 1.558583ms message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:12Z" - latency: 897.113µs message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:12Z" - latency: 1.655867ms message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:12Z" - latency: 1.053417ms message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:12Z" - latency: 963.906µs message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:12Z" - latency: 937.779µs message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-network-check-target-ip-10-0-136-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "33228" uid: e3153dba-5ea9-4666-bf0c-f892cbd0526f spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:10:12Z" message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.490484ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:12Z" - latency: 2.35775ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:12Z" - latency: 2.605376ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:12Z" - latency: 2.390764ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:12Z" - latency: 2.765635ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:12Z" - latency: 2.184591ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:12Z" - latency: 2.51015ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:12Z" - latency: 2.570997ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:12Z" - latency: 2.372199ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:12Z" - latency: 2.351095ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-network-check-target-ip-10-0-142-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "33227" uid: 97eb16dc-e77b-4740-adc2-e306c853327d spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:10:12Z" message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.151503ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:12Z" - latency: 1.958736ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:12Z" - latency: 2.54742ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:12Z" - latency: 2.022386ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:12Z" - latency: 2.340994ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:12Z" - latency: 2.118503ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:12Z" - latency: 1.983602ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:12Z" - latency: 2.0148ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:12Z" - latency: 1.974333ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:12Z" - latency: 1.975804ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-182-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-182.ec2.internal uid: 3ebd694f-3dee-4bf7-a5f5-cb2ec6225166 resourceVersion: "35683" uid: 036a1a72-0131-4199-88d5-dad8ac51a728 spec: sourcePod: network-check-source-685456655f-kf5w5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:09:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.858µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:51:12Z" - latency: 1.884071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:51:12Z" - latency: 1.12863ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:12Z" - latency: 1.835973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:50:12Z" - latency: 825.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:49:12Z" - latency: 1.839952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:49:12Z" - latency: 835.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:12Z" - latency: 1.825773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:48:12Z" - latency: 828.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:12Z" - latency: 1.702027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:47:12Z" kind: List metadata: resourceVersion: ""