apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "21638" uid: 7642e639-95d5-4351-ae48-9c9d62a11ecb spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T22:01:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.277µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:25Z" - latency: 1.022371ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:25Z" - latency: 1.322606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:25Z" - latency: 1.024521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 1.119632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 877.667µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 929.67µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 2.166334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 1.15983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:25Z" - latency: 979.591µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "20279" uid: 0e9367ec-fbd5-474f-a5cc-fbb3c78f8417 spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T22:00:25Z" message: 'load-balancer-api-external: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.541676ms message: 'load-balancer-api-external: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 7.56165ms message: 'load-balancer-api-external: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:12:25Z" - latency: 4.206789ms message: 'load-balancer-api-external: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 6.26593ms message: 'load-balancer-api-external: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:11:25Z" - latency: 4.963498ms message: 'load-balancer-api-external: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 8.585764ms message: 'load-balancer-api-external: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:10:25Z" - latency: 6.850031ms message: 'load-balancer-api-external: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 6.187858ms message: 'load-balancer-api-external: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:09:25Z" - latency: 5.871621ms message: 'load-balancer-api-external: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 9.161633ms message: 'load-balancer-api-external: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:08:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "20278" uid: a82252ff-3031-4167-84e7-7a965ced2fee spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T22:00:25Z" message: 'load-balancer-api-internal: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.725865ms message: 'load-balancer-api-internal: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 7.579757ms message: 'load-balancer-api-internal: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:12:25Z" - latency: 4.221297ms message: 'load-balancer-api-internal: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 6.177133ms message: 'load-balancer-api-internal: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:11:25Z" - latency: 4.101143ms message: 'load-balancer-api-internal: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 8.488791ms message: 'load-balancer-api-internal: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:10:25Z" - latency: 6.833754ms message: 'load-balancer-api-internal: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 6.098948ms message: 'load-balancer-api-internal: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:09:25Z" - latency: 5.831068ms message: 'load-balancer-api-internal: tcp connection to afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 9.187513ms message: 'load-balancer-api-internal: resolved host name afa9cb912f26b42e1ac25d90227facc3-643ce8ebed250d6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:08:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-network-check-target-ip-10-0-138-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "21634" uid: b385d14c-d6a2-46ce-b9a8-1752cb27312b spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:01:25Z" message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.119561ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:25Z" - latency: 877.909µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:25Z" - latency: 896.248µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:25Z" - latency: 963.806µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 924.197µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 889.338µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 786.665µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 906.951µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 783.23µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:25Z" - latency: 916.446µs message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-network-check-target-ip-10-0-139-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "21635" uid: cf2037ee-80a9-4bb3-86d2-5a7ead31a5f8 spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:01:25Z" message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.198543ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:25Z" - latency: 2.172026ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:25Z" - latency: 2.079511ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:25Z" - latency: 2.309349ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 2.198113ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 2.294821ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 2.174148ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 2.981227ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 2.513035ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:25Z" - latency: 2.200632ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-network-check-target-ip-10-0-140-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "21636" uid: d0c04554-bcfd-4bbc-b9e8-3fe6956ab3aa spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:01:25Z" message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286229ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:15:25Z" - latency: 2.190135ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:14:25Z" - latency: 2.246632ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:13:25Z" - latency: 2.248118ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 2.231002ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 2.255105ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 2.405207ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 2.949512ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 2.552036ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:25Z" - latency: 2.306774ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:54:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-41-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-41.ec2.internal uid: 5f46c33b-81cc-407f-a78e-c8fcf759e04e resourceVersion: "20277" uid: b17f8983-df37-482a-8d1f-6626a5930c25 spec: sourcePod: network-check-source-7bc5b6bf85-5zwt4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T22:00:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:12:25Z" - latency: 1.904265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:12:25Z" - latency: 877.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:11:25Z" - latency: 1.711668ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:11:25Z" - latency: 793.443µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:10:25Z" - latency: 1.649246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:10:25Z" - latency: 800.452µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:09:25Z" - latency: 1.577614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:09:25Z" - latency: 1.057229ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:08:25Z" - latency: 3.016075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:08:25Z" kind: List metadata: resourceVersion: ""