apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T21:12:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "69307" uid: f848b6ec-fbc3-42c2-ade4-605267b9001a spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T21:19:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.237753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:01:40Z" - latency: 1.655688ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:00:40Z" - latency: 1.329555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:59:40Z" - latency: 1.350395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:58:40Z" - latency: 1.886588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:57:40Z" - latency: 887.089µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:56:40Z" - latency: 1.09139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:55:40Z" - latency: 1.032482ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:54:40Z" - latency: 1.084819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:53:40Z" - latency: 937.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T21:12:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "75300" uid: f37ee36a-5f64-4299-ae66-3b4a960c455e spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T21:18:40Z" message: 'load-balancer-api-external: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.164599ms message: 'load-balancer-api-external: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:06:40Z" - latency: 13.084879ms message: 'load-balancer-api-external: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:06:40Z" - latency: 4.065354ms message: 'load-balancer-api-external: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:05:40Z" - latency: 7.480183ms message: 'load-balancer-api-external: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:05:40Z" - latency: 5.006147ms message: 'load-balancer-api-external: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:04:40Z" - latency: 7.275211ms message: 'load-balancer-api-external: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:04:40Z" - latency: 4.844418ms message: 'load-balancer-api-external: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:03:40Z" - latency: 6.698669ms message: 'load-balancer-api-external: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:03:40Z" - latency: 5.04517ms message: 'load-balancer-api-external: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:02:40Z" - latency: 6.814947ms message: 'load-balancer-api-external: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:02:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T21:12:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "75299" uid: c61fd833-1547-483a-82ce-4923bf87ab5e spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T21:18:40Z" message: 'load-balancer-api-internal: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.185269ms message: 'load-balancer-api-internal: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:06:40Z" - latency: 13.116655ms message: 'load-balancer-api-internal: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:06:40Z" - latency: 4.803037ms message: 'load-balancer-api-internal: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:05:40Z" - latency: 7.494053ms message: 'load-balancer-api-internal: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:05:40Z" - latency: 6.409275ms message: 'load-balancer-api-internal: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:04:40Z" - latency: 7.221667ms message: 'load-balancer-api-internal: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:04:40Z" - latency: 4.924997ms message: 'load-balancer-api-internal: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:03:40Z" - latency: 6.609839ms message: 'load-balancer-api-internal: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:03:40Z" - latency: 5.037343ms message: 'load-balancer-api-internal: tcp connection to a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:02:40Z" - latency: 6.759941ms message: 'load-balancer-api-internal: resolved host name a2372d7ae419449aca06ea13091ff12e-ea0095fb6ecabfb5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T22:02:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T22:05:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-network-check-target-ip-10-0-128-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "73409" uid: 9cde425e-7391-4021-8f1e-64adc6d2e397 spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: 10.133.0.3:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T21:12:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-network-check-target-ip-10-0-129-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "69305" uid: de71494e-572e-463d-b2c5-66634c07b5ad spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T21:19:40Z" message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.975574ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:01:40Z" - latency: 2.371147ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:00:40Z" - latency: 2.068379ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:59:40Z" - latency: 2.290052ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:58:40Z" - latency: 2.305254ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:57:40Z" - latency: 2.563491ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:56:40Z" - latency: 2.102371ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:55:40Z" - latency: 1.890759ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:54:40Z" - latency: 2.106725ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:53:40Z" - latency: 1.946882ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T21:12:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-network-check-target-ip-10-0-140-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "69304" uid: 0555a417-405c-4333-9d46-8bb1d5c4bfd3 spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T21:19:40Z" message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.53µs message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:01:40Z" - latency: 1.318296ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:00:40Z" - latency: 1.515854ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:59:40Z" - latency: 1.012759ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:58:40Z" - latency: 1.044726ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:57:40Z" - latency: 1.257492ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:56:40Z" - latency: 1.028596ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:55:40Z" - latency: 1.036011ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:54:40Z" - latency: 1.415376ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:53:40Z" - latency: 1.625319ms message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T21:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T21:12:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-117.ec2.internal uid: fc01fc90-0694-4395-9971-3813ef5dd985 resourceVersion: "75298" uid: 6eb5f716-3a08-49f6-aeaf-6d75e6a28819 spec: sourcePod: network-check-source-7bc5b6bf85-x87k6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T21:18:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.575µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:06:40Z" - latency: 1.931614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T22:06:40Z" - latency: 795.865µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:05:40Z" - latency: 1.986376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T22:05:40Z" - latency: 1.057569ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:04:40Z" - latency: 2.162815ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T22:04:40Z" - latency: 907.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:03:40Z" - latency: 1.846424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T22:03:40Z" - latency: 1.098179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T22:02:40Z" - latency: 1.767021ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T22:02:40Z" kind: List metadata: resourceVersion: ""