apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "73058" uid: bb792963-497d-490f-b279-38b9f7d0983b spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-03T23:44:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.147171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:26:36Z" - latency: 1.346664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:25:36Z" - latency: 949.995µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:24:36Z" - latency: 1.089663ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:23:36Z" - latency: 996.434µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:22:36Z" - latency: 1.193822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:21:36Z" - latency: 900.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:20:36Z" - latency: 1.22946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:19:36Z" - latency: 1.34634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:18:36Z" - latency: 915.415µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:17:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "78610" uid: b656bdb9-7eaa-4b46-a6c3-25be41470358 spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-03T23:43:36Z" message: 'load-balancer-api-external: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.490517ms message: 'load-balancer-api-external: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:31:36Z" - latency: 7.178124ms message: 'load-balancer-api-external: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:31:36Z" - latency: 5.072123ms message: 'load-balancer-api-external: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:30:36Z" - latency: 8.796777ms message: 'load-balancer-api-external: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:30:36Z" - latency: 5.521424ms message: 'load-balancer-api-external: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:29:36Z" - latency: 8.538365ms message: 'load-balancer-api-external: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:29:36Z" - latency: 3.579699ms message: 'load-balancer-api-external: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:28:36Z" - latency: 9.284442ms message: 'load-balancer-api-external: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:28:36Z" - latency: 3.723062ms message: 'load-balancer-api-external: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:27:36Z" - latency: 10.348848ms message: 'load-balancer-api-external: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:27:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "78611" uid: 38bf3388-2a27-400d-9f44-cd3ef8ff31b4 spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-03T23:43:36Z" message: 'load-balancer-api-internal: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.740078ms message: 'load-balancer-api-internal: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:31:36Z" - latency: 7.262001ms message: 'load-balancer-api-internal: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:31:36Z" - latency: 5.09782ms message: 'load-balancer-api-internal: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:30:36Z" - latency: 8.677451ms message: 'load-balancer-api-internal: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:30:36Z" - latency: 4.092977ms message: 'load-balancer-api-internal: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:29:36Z" - latency: 8.518174ms message: 'load-balancer-api-internal: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:29:36Z" - latency: 14.840442ms message: 'load-balancer-api-internal: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:28:36Z" - latency: 9.215605ms message: 'load-balancer-api-internal: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:28:36Z" - latency: 3.368707ms message: 'load-balancer-api-internal: tcp connection to a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:27:36Z" - latency: 10.373309ms message: 'load-balancer-api-internal: resolved host name a695e833015344747bbd573d6f2375a9-9cebbf673fcd063d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T00:27:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-136-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "73055" uid: d2e136c3-7550-4589-8816-d75eb5b5b729 spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-03T23:44:36Z" message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.267957ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:26:36Z" - latency: 1.03838ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:25:36Z" - latency: 772.041µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:24:36Z" - latency: 1.073456ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:23:36Z" - latency: 1.613541ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:22:36Z" - latency: 1.436654ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:21:36Z" - latency: 1.592287ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:20:36Z" - latency: 866.79µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:19:36Z" - latency: 777.033µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:18:36Z" - latency: 1.266731ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:17:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-138-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "73057" uid: ad29dd70-b78f-48b5-9c2d-145b50c08d66 spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-03T23:44:36Z" message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.067526ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:26:36Z" - latency: 2.159584ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:25:36Z" - latency: 2.249861ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:24:36Z" - latency: 2.222006ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:23:36Z" - latency: 2.031042ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:22:36Z" - latency: 2.295692ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:21:36Z" - latency: 2.021852ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:20:36Z" - latency: 2.177332ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:19:36Z" - latency: 2.867628ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:18:36Z" - latency: 2.238961ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:17:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-143-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "73056" uid: 326018b3-ecd9-4905-9a76-5a778a84ef64 spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-03T23:44:36Z" message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.625133ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:26:36Z" - latency: 1.618397ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:25:36Z" - latency: 2.043729ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:24:36Z" - latency: 2.064341ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:23:36Z" - latency: 1.87346ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:22:36Z" - latency: 2.24661ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:21:36Z" - latency: 1.531129ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:20:36Z" - latency: 1.8784ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:19:36Z" - latency: 1.852728ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:18:36Z" - latency: 1.942735ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:17:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T23:37:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: db2a231e-457d-474c-bb61-b9ffd0b2c2c0 resourceVersion: "78609" uid: aeddb825-0fe5-40c8-a555-27851a6a71c6 spec: sourcePod: network-check-source-65bdbbff45-c6qx5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-03T23:43:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.274357ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:31:36Z" - latency: 1.755913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:31:36Z" - latency: 1.19232ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:30:36Z" - latency: 1.822768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:30:36Z" - latency: 1.076505ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:29:36Z" - latency: 2.088611ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:29:36Z" - latency: 967.134µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:28:36Z" - latency: 1.930106ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:28:36Z" - latency: 1.001922ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T00:27:36Z" - latency: 2.58611ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T00:27:36Z" kind: List metadata: resourceVersion: ""