apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "42537" uid: f53f97d4-49cd-471a-b2a2-ee92372e01af spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T14:15:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.162151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 1.148689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 884.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 1.235913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:33:37Z" - latency: 1.243307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:32:37Z" - latency: 778.967µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:31:37Z" - latency: 1.202391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:30:37Z" - latency: 1.185447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:29:37Z" - latency: 950.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:28:37Z" - latency: 1.107651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:27:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "44960" uid: da8d15f0-3501-45d1-9f41-5846a015a5d9 spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T14:14:37Z" message: 'load-balancer-api-external: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.062516ms message: 'load-balancer-api-external: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:38:37Z" - latency: 7.614295ms message: 'load-balancer-api-external: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:38:37Z" - latency: 7.290377ms message: 'load-balancer-api-external: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:37:37Z" - latency: 9.898159ms message: 'load-balancer-api-external: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:37:37Z" - latency: 4.359935ms message: 'load-balancer-api-external: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 8.478475ms message: 'load-balancer-api-external: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:36:37Z" - latency: 8.937231ms message: 'load-balancer-api-external: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 7.567874ms message: 'load-balancer-api-external: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:35:37Z" - latency: 5.010619ms message: 'load-balancer-api-external: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 7.430684ms message: 'load-balancer-api-external: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:34:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "44959" uid: 1c3a8dca-0c4e-4b12-8115-fcffd81484b7 spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T14:14:37Z" message: 'load-balancer-api-internal: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.319406ms message: 'load-balancer-api-internal: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:38:37Z" - latency: 7.640916ms message: 'load-balancer-api-internal: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:38:37Z" - latency: 7.214883ms message: 'load-balancer-api-internal: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:37:37Z" - latency: 9.94204ms message: 'load-balancer-api-internal: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:37:37Z" - latency: 4.944904ms message: 'load-balancer-api-internal: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 8.379965ms message: 'load-balancer-api-internal: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:36:37Z" - latency: 7.379063ms message: 'load-balancer-api-internal: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 7.634061ms message: 'load-balancer-api-internal: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:35:37Z" - latency: 4.920057ms message: 'load-balancer-api-internal: tcp connection to afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 7.489484ms message: 'load-balancer-api-internal: resolved host name afe3c34c5a2034bc680dc9ef42d233d2-f38bc591d3b8548a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T14:34:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-ip-10-0-136-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "42536" uid: 34e75eb3-d39e-42d4-9ae1-edaa7cfc9612 spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T14:15:37Z" message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.160099ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 1.472034ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 859.553µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 873.512µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:33:37Z" - latency: 975.323µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:32:37Z" - latency: 1.729272ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:31:37Z" - latency: 761.225µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:30:37Z" - latency: 797.879µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:29:37Z" - latency: 1.054648ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:28:37Z" - latency: 1.202003ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:27:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-ip-10-0-141-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "42534" uid: 8d9fbe07-5c7c-45d0-80c2-3fb97bed9b4c spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T14:15:37Z" message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.077032ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 1.694882ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 2.12883ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 2.375971ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:33:37Z" - latency: 2.326806ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:32:37Z" - latency: 2.120359ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:31:37Z" - latency: 2.434148ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:30:37Z" - latency: 2.191596ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:29:37Z" - latency: 2.18954ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:28:37Z" - latency: 2.541462ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:27:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-ip-10-0-143-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "42535" uid: bb861576-9597-4e15-b472-e172006b9158 spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T14:15:37Z" message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.92503ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 2.078058ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 1.864998ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 2.213526ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:33:37Z" - latency: 1.986075ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:32:37Z" - latency: 1.84204ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:31:37Z" - latency: 1.978939ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:30:37Z" - latency: 1.913695ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:29:37Z" - latency: 2.007195ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:28:37Z" - latency: 2.182955ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:27:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T14:08:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: c0c7b990-11a1-4171-a2f1-1c9b9f80a11e resourceVersion: "44958" uid: 22cdca0c-21a5-449e-9fb8-ef0ecda45e9f spec: sourcePod: network-check-source-7f44b6dd87-68ntw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T14:14:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 694.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:38:37Z" - latency: 2.08259ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T14:38:37Z" - latency: 798.677µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:37:37Z" - latency: 1.754165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T14:37:37Z" - latency: 847.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:36:37Z" - latency: 1.619549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T14:36:37Z" - latency: 759.173µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:35:37Z" - latency: 1.39965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T14:35:37Z" - latency: 955.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T14:34:37Z" - latency: 1.585076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T14:34:37Z" kind: List metadata: resourceVersion: ""