apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "20140"
    uid: 255d7ead-6aca-411b-b59e-c5366401a0c7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 748.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 967.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:15Z"
    - latency: 1.035756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:15Z"
    - latency: 1.017831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:15Z"
    - latency: 1.408919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:15Z"
    - latency: 827.051µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:15Z"
    - latency: 1.311148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:15Z"
    - latency: 997.801µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:15Z"
    - latency: 1.196558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "21665"
    uid: 94e57142-35de-43b9-9cca-9172c6cf13fe
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:46:15Z"
      message: 'load-balancer-api-external: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.46435ms
      message: 'load-balancer-api-external: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:15Z"
    - latency: 12.678786ms
      message: 'load-balancer-api-external: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:04:15Z"
    - latency: 5.282745ms
      message: 'load-balancer-api-external: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:15Z"
    - latency: 9.665828ms
      message: 'load-balancer-api-external: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:03:15Z"
    - latency: 4.290002ms
      message: 'load-balancer-api-external: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:15Z"
    - latency: 9.10566ms
      message: 'load-balancer-api-external: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:02:15Z"
    - latency: 6.128424ms
      message: 'load-balancer-api-external: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 9.247976ms
      message: 'load-balancer-api-external: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 4.715357ms
      message: 'load-balancer-api-external: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 8.813781ms
      message: 'load-balancer-api-external: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:00:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "21666"
    uid: 54369f4a-cf94-4973-83f0-4f925ab15628
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:46:15Z"
      message: 'load-balancer-api-internal: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.472794ms
      message: 'load-balancer-api-internal: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:15Z"
    - latency: 12.775619ms
      message: 'load-balancer-api-internal: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:04:15Z"
    - latency: 3.25841ms
      message: 'load-balancer-api-internal: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:15Z"
    - latency: 9.593468ms
      message: 'load-balancer-api-internal: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:03:15Z"
    - latency: 4.482278ms
      message: 'load-balancer-api-internal: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:15Z"
    - latency: 9.150308ms
      message: 'load-balancer-api-internal: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:02:15Z"
    - latency: 6.182461ms
      message: 'load-balancer-api-internal: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 9.15698ms
      message: 'load-balancer-api-internal: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 4.844103ms
      message: 'load-balancer-api-internal: tcp connection to a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 8.692996ms
      message: 'load-balancer-api-internal: resolved host name a85c8a7b654fc463b9b9d0dd5c20077a-828be820d55fdc9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:00:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-network-check-target-ip-10-0-135-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "20139"
    uid: 8b8da98f-ecdb-44de-8aa8-66d78c86c8d8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:15Z"
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297403ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 2.04998ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 2.510762ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:15Z"
    - latency: 2.465182ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:15Z"
    - latency: 2.05406ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:15Z"
    - latency: 2.260817ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:15Z"
    - latency: 2.363199ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:15Z"
    - latency: 2.712844ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:15Z"
    - latency: 2.473096ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:15Z"
    - latency: 2.110463ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-network-check-target-ip-10-0-136-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "20138"
    uid: fa1ecff4-6e2b-492e-bc03-f948e741d565
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:15Z"
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.866864ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 1.93263ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 2.167806ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:15Z"
    - latency: 2.430998ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:15Z"
    - latency: 2.135598ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:15Z"
    - latency: 2.394922ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:15Z"
    - latency: 2.064367ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:15Z"
    - latency: 2.015963ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:15Z"
    - latency: 2.092228ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:15Z"
    - latency: 2.042798ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-network-check-target-ip-10-0-140-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "20137"
    uid: 9e4778fa-4007-4908-bb06-c8aa9cc3b7d7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:15Z"
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.717µs
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 852.584µs
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 729.063µs
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:15Z"
    - latency: 888.617µs
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:15Z"
    - latency: 1.079657ms
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:15Z"
    - latency: 969.695µs
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:15Z"
    - latency: 1.056481ms
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:15Z"
    - latency: 1.54198ms
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:15Z"
    - latency: 1.442745ms
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:15Z"
    - latency: 938.141µs
      message: 'network-check-target-ip-10-0-140-218: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:40:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-218.ec2.internal
      uid: 1120f032-3555-4c21-839a-7d588a6bede1
    resourceVersion: "21664"
    uid: 7282b904-4e3e-423c-b33e-1ca0e7b23414
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mvgbz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:46:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 949.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:15Z"
    - latency: 2.017512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:04:15Z"
    - latency: 642.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:15Z"
    - latency: 2.505667ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:03:15Z"
    - latency: 785.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:15Z"
    - latency: 1.500781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:02:15Z"
    - latency: 956.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 1.759072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:01:15Z"
    - latency: 962.754µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:15Z"
    - latency: 1.569172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:00:15Z"
kind: List
metadata:
  resourceVersion: ""