apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "21542" uid: a2b557e1-5c1c-40e6-bebb-00b00cddbb81 spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T14:25:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:51Z" - latency: 1.271368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:51Z" - latency: 931.707µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:51Z" - latency: 1.430805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 851.693µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 975.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 982.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 1.207182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 866.905µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:51Z" - latency: 1.075821ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "20208" uid: 6918d92f-d61d-4d0e-b372-cbe86b3063d1 spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T14:24:51Z" message: 'load-balancer-api-external: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.959619ms message: 'load-balancer-api-external: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 8.755821ms message: 'load-balancer-api-external: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:36:51Z" - latency: 8.134673ms message: 'load-balancer-api-external: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 8.035641ms message: 'load-balancer-api-external: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:51Z" - latency: 5.623842ms message: 'load-balancer-api-external: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 8.24559ms message: 'load-balancer-api-external: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:51Z" - latency: 6.232115ms message: 'load-balancer-api-external: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 8.222154ms message: 'load-balancer-api-external: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:51Z" - latency: 6.402746ms message: 'load-balancer-api-external: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 8.795045ms message: 'load-balancer-api-external: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "20207" uid: d8dd103e-4030-42cc-9b78-5845f50435f0 spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T14:24:51Z" message: 'load-balancer-api-internal: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.991102ms message: 'load-balancer-api-internal: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 8.672745ms message: 'load-balancer-api-internal: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:36:51Z" - latency: 5.265668ms message: 'load-balancer-api-internal: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 7.968728ms message: 'load-balancer-api-internal: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:51Z" - latency: 5.55583ms message: 'load-balancer-api-internal: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 8.389335ms message: 'load-balancer-api-internal: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:51Z" - latency: 5.104761ms message: 'load-balancer-api-internal: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 8.107361ms message: 'load-balancer-api-internal: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:51Z" - latency: 6.359829ms message: 'load-balancer-api-internal: tcp connection to a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 8.875247ms message: 'load-balancer-api-internal: resolved host name a65c9a681110343c599ba384f66f4daa-92c0418ae4275bd5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-network-check-target-ip-10-0-130-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "21541" uid: 66c37ec1-25c7-4037-8267-2d57ee7c0ee2 spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:25:51Z" message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.359288ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:51Z" - latency: 2.473079ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:51Z" - latency: 2.137413ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:51Z" - latency: 2.284899ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 2.735448ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 2.350721ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 2.160177ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 2.457462ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 2.171445ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:51Z" - latency: 2.409478ms message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-network-check-target-ip-10-0-136-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "21539" uid: 05dfdcf4-6543-4c02-b84b-8d306c5fde05 spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:25:51Z" message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.019µs message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:51Z" - latency: 1.620254ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:51Z" - latency: 1.219811ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:51Z" - latency: 1.590188ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 929.191µs message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 745.424µs message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 915.08µs message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 1.26845ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 1.375818ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:51Z" - latency: 919.979µs message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-network-check-target-ip-10-0-138-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "21540" uid: 59d98ec9-9207-4642-b6ea-52aaff13b621 spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:25:51Z" message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.305102ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:51Z" - latency: 2.507097ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:51Z" - latency: 2.468633ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:51Z" - latency: 2.830433ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 2.558415ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 2.110134ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 2.293464ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 2.486477ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 2.624147ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:51Z" - latency: 2.238984ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-174-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-174.ec2.internal uid: 3beda1ea-8225-40d2-a1ae-dbb468cecc1c resourceVersion: "20205" uid: 8717177b-b469-46b9-ba96-9bbde421567b spec: sourcePod: network-check-source-56499946bc-hknk7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T14:24:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 785.427µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:51Z" - latency: 1.640359ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:36:51Z" - latency: 926.611µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:51Z" - latency: 1.814017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:51Z" - latency: 724.017µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:51Z" - latency: 1.606333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:51Z" - latency: 750.116µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:51Z" - latency: 1.637622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:51Z" - latency: 872.068µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:51Z" - latency: 2.187535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:51Z" kind: List metadata: resourceVersion: ""