apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "22277" uid: b0e0efed-9f1c-4b11-a204-0e7b024c6340 spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T21:30:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.15286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:44:13Z" - latency: 1.200106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:43:13Z" - latency: 1.029832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:42:13Z" - latency: 1.530973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 920.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 1.176287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 964.222µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 1.762363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 1.31153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:36:13Z" - latency: 1.037077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:35:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "20853" uid: 01e33ed0-2e51-4514-88a1-d8ca537b935e spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T21:29:13Z" message: 'load-balancer-api-external: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.438846ms message: 'load-balancer-api-external: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 9.083399ms message: 'load-balancer-api-external: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:41:13Z" - latency: 5.317307ms message: 'load-balancer-api-external: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 7.727113ms message: 'load-balancer-api-external: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:40:13Z" - latency: 4.067773ms message: 'load-balancer-api-external: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 9.293219ms message: 'load-balancer-api-external: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:39:13Z" - latency: 3.934763ms message: 'load-balancer-api-external: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 7.090351ms message: 'load-balancer-api-external: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:38:13Z" - latency: 4.379345ms message: 'load-balancer-api-external: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 6.924523ms message: 'load-balancer-api-external: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:37:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "20852" uid: 893a3a1e-aed3-4e2a-8392-f2464abbcda1 spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T21:29:13Z" message: 'load-balancer-api-internal: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.493011ms message: 'load-balancer-api-internal: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 9.123819ms message: 'load-balancer-api-internal: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:41:13Z" - latency: 5.327963ms message: 'load-balancer-api-internal: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 7.665441ms message: 'load-balancer-api-internal: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:40:13Z" - latency: 5.04107ms message: 'load-balancer-api-internal: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 9.214185ms message: 'load-balancer-api-internal: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:39:13Z" - latency: 4.577034ms message: 'load-balancer-api-internal: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 7.048509ms message: 'load-balancer-api-internal: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:38:13Z" - latency: 4.077476ms message: 'load-balancer-api-internal: tcp connection to a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 6.881179ms message: 'load-balancer-api-internal: resolved host name a7e3199aad32b482c8666c4d0c1809b6-624ab16877b1cad8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T21:37:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-network-check-target-ip-10-0-133-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "22276" uid: 66b63d04-0044-4d36-8235-869243d17e8e spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T21:30:13Z" message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.52303ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:44:13Z" - latency: 2.382371ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:43:13Z" - latency: 2.02448ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:42:13Z" - latency: 2.241395ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 2.29394ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 2.035127ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 2.577922ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 2.281888ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 2.282864ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:36:13Z" - latency: 2.216541ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:35:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-network-check-target-ip-10-0-135-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "22275" uid: 7cebe378-1356-4850-a6e3-58a7903419a3 spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T21:30:13Z" message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.61826ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:44:13Z" - latency: 2.387188ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:43:13Z" - latency: 1.947513ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:42:13Z" - latency: 2.337795ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 1.897594ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 2.348701ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 1.921188ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 2.273465ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 2.074746ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:36:13Z" - latency: 2.490168ms message: 'network-check-target-ip-10-0-135-227: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:35:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-network-check-target-ip-10-0-137-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "22274" uid: 1a0e3455-ee59-4ade-b6f1-12268fe45c9c spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T21:30:13Z" message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.392µs message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:44:13Z" - latency: 1.413892ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:43:13Z" - latency: 833.068µs message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:42:13Z" - latency: 1.47408ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 1.339191ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 1.176212ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 1.061406ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 2.22934ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 1.357793ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:36:13Z" - latency: 838.062µs message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:35:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T21:23:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-60-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-60.ec2.internal uid: 12350814-983a-4652-9cdc-f6234171fc63 resourceVersion: "20851" uid: 221eb891-bc4b-4438-9ebc-27bdf5c4ac25 spec: sourcePod: network-check-source-989f8b8dc-8nzhj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T21:29:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.646µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:41:13Z" - latency: 2.162345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T21:41:13Z" - latency: 1.014634ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:40:13Z" - latency: 1.717517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T21:40:13Z" - latency: 879.191µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:39:13Z" - latency: 1.704312ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T21:39:13Z" - latency: 1.221957ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:38:13Z" - latency: 2.117439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T21:38:13Z" - latency: 1.174226ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T21:37:13Z" - latency: 1.691495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T21:37:13Z" kind: List metadata: resourceVersion: ""