apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "18161" uid: 1c9d38c6-2e6d-41d9-a8f7-354ec53b4de0 spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T13:59:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.329µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 1.243373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:05:54Z" - latency: 1.263626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:04:54Z" - latency: 1.034282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:03:54Z" - latency: 1.086212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:02:54Z" - latency: 843.967µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:01:54Z" - latency: 902.03µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:00:54Z" - latency: 831.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:59:54Z" - latency: 1.234538ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:58:54Z" - latency: 932.794µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "20310" uid: 2f336069-77bb-4732-9d00-d21a27bf3fdd spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T13:58:54Z" message: 'load-balancer-api-external: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.853806ms message: 'load-balancer-api-external: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:10:54Z" - latency: 8.322524ms message: 'load-balancer-api-external: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:10:54Z" - latency: 5.313426ms message: 'load-balancer-api-external: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:09:54Z" - latency: 6.849524ms message: 'load-balancer-api-external: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:09:54Z" - latency: 5.14746ms message: 'load-balancer-api-external: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:08:54Z" - latency: 6.182018ms message: 'load-balancer-api-external: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:08:54Z" - latency: 5.246381ms message: 'load-balancer-api-external: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:07:54Z" - latency: 6.496523ms message: 'load-balancer-api-external: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:07:54Z" - latency: 5.123773ms message: 'load-balancer-api-external: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 6.600808ms message: 'load-balancer-api-external: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "20309" uid: 2e0e7ca5-2986-43df-a93f-e4a031c7b9cf spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T13:58:54Z" message: 'load-balancer-api-internal: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.861733ms message: 'load-balancer-api-internal: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:10:54Z" - latency: 8.35731ms message: 'load-balancer-api-internal: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:10:54Z" - latency: 5.304037ms message: 'load-balancer-api-internal: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:09:54Z" - latency: 6.865049ms message: 'load-balancer-api-internal: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:09:54Z" - latency: 5.157979ms message: 'load-balancer-api-internal: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:08:54Z" - latency: 6.157106ms message: 'load-balancer-api-internal: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:08:54Z" - latency: 5.217271ms message: 'load-balancer-api-internal: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:07:54Z" - latency: 6.578106ms message: 'load-balancer-api-internal: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:07:54Z" - latency: 5.108745ms message: 'load-balancer-api-internal: tcp connection to a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 6.525818ms message: 'load-balancer-api-internal: resolved host name a9d161ee2dba140a7b42473fc25f2b99-16b70a99d65af607.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-128-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "18160" uid: d91e4225-a72c-4c75-b431-337871cad34b spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T13:59:54Z" message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.17907ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 2.177661ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:05:54Z" - latency: 2.016435ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:04:54Z" - latency: 2.555137ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:03:54Z" - latency: 2.281853ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:02:54Z" - latency: 2.197424ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:01:54Z" - latency: 2.128196ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:00:54Z" - latency: 1.996508ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:59:54Z" - latency: 2.261724ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:58:54Z" - latency: 1.991133ms message: 'network-check-target-ip-10-0-128-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-130-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "18158" uid: a6d617fb-64ce-4220-8d83-e76412f7e205 spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T13:59:54Z" message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.001µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 823.447µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:05:54Z" - latency: 964.424µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:04:54Z" - latency: 927.598µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:03:54Z" - latency: 944.044µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:02:54Z" - latency: 1.470699ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:01:54Z" - latency: 818.987µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:00:54Z" - latency: 885.687µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:59:54Z" - latency: 1.702814ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:58:54Z" - latency: 1.122377ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-140-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "18159" uid: b5f685f8-3738-451f-adae-75aad656dda5 spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T13:59:54Z" message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.906535ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 1.912018ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:05:54Z" - latency: 1.982015ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:04:54Z" - latency: 2.094865ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:03:54Z" - latency: 1.984926ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:02:54Z" - latency: 1.853144ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:01:54Z" - latency: 1.973731ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:00:54Z" - latency: 1.654348ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:59:54Z" - latency: 1.725228ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:58:54Z" - latency: 1.823325ms message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T13:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:52:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: 61ef988b-c361-4a0b-80f7-b12922eebc2d resourceVersion: "20308" uid: ce9752ae-bff5-478b-a178-b856fea48ed0 spec: sourcePod: network-check-source-7f44b6dd87-ktk7m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T13:58:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.231µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:10:54Z" - latency: 1.534961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:10:54Z" - latency: 1.101376ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:09:54Z" - latency: 1.563622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:09:54Z" - latency: 797.057µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:08:54Z" - latency: 1.48913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:08:54Z" - latency: 955.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:07:54Z" - latency: 1.562731ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:07:54Z" - latency: 1.27849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:06:54Z" - latency: 1.74034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:06:54Z" kind: List metadata: resourceVersion: ""