apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "19315"
    uid: dfb80017-f9e1-4cee-a542-38fa3d920860
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:27:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.216355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 995.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 1.014141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:39:19Z"
    - latency: 883.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:38:19Z"
    - latency: 1.358807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:37:19Z"
    - latency: 1.066218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:36:19Z"
    - latency: 1.094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:35:19Z"
    - latency: 1.229173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:34:19Z"
    - latency: 899.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:33:19Z"
    - latency: 913.79µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "20547"
    uid: c0600f6f-6c6f-41a6-b4fb-86825b624e81
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:26:19Z"
      message: 'load-balancer-api-external: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.115073ms
      message: 'load-balancer-api-external: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:44:19Z"
    - latency: 6.787519ms
      message: 'load-balancer-api-external: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:44:19Z"
    - latency: 4.085381ms
      message: 'load-balancer-api-external: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:43:19Z"
    - latency: 8.529588ms
      message: 'load-balancer-api-external: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:43:19Z"
    - latency: 5.767857ms
      message: 'load-balancer-api-external: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:42:19Z"
    - latency: 8.318435ms
      message: 'load-balancer-api-external: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:42:19Z"
    - latency: 4.282216ms
      message: 'load-balancer-api-external: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 8.120296ms
      message: 'load-balancer-api-external: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 5.432283ms
      message: 'load-balancer-api-external: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 7.692808ms
      message: 'load-balancer-api-external: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "20546"
    uid: 55e13647-5594-49d6-a1d4-0f7a4ca92cd5
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:26:19Z"
      message: 'load-balancer-api-internal: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.092571ms
      message: 'load-balancer-api-internal: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:44:19Z"
    - latency: 6.83212ms
      message: 'load-balancer-api-internal: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:44:19Z"
    - latency: 2.94813ms
      message: 'load-balancer-api-internal: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:43:19Z"
    - latency: 8.472957ms
      message: 'load-balancer-api-internal: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:43:19Z"
    - latency: 5.77073ms
      message: 'load-balancer-api-internal: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:42:19Z"
    - latency: 8.400021ms
      message: 'load-balancer-api-internal: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:42:19Z"
    - latency: 5.606903ms
      message: 'load-balancer-api-internal: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 8.085994ms
      message: 'load-balancer-api-internal: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 7.524865ms
      message: 'load-balancer-api-internal: tcp connection to a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 7.72568ms
      message: 'load-balancer-api-internal: resolved host name a3fa8d4eb77854ae08ff748804db61b3-f41a24b6b039eb81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-network-check-target-ip-10-0-133-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "19312"
    uid: 16d59188-df58-46e8-bcda-75757cd5a915
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:27:19Z"
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 817.277µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 886.612µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 1.043951ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:39:19Z"
    - latency: 910.709µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:38:19Z"
    - latency: 824.297µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:37:19Z"
    - latency: 915.279µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:36:19Z"
    - latency: 1.22985ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:35:19Z"
    - latency: 1.333875ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:34:19Z"
    - latency: 957.09µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:33:19Z"
    - latency: 902.457µs
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-network-check-target-ip-10-0-137-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "19314"
    uid: 2124744d-6499-419b-b6db-e768f72ad67e
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:27:19Z"
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.925377ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 2.196883ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 2.011307ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:39:19Z"
    - latency: 1.720266ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:38:19Z"
    - latency: 2.217261ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:37:19Z"
    - latency: 2.838099ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:36:19Z"
    - latency: 2.10261ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:35:19Z"
    - latency: 2.204756ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:34:19Z"
    - latency: 2.183224ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:33:19Z"
    - latency: 1.941298ms
      message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-network-check-target-ip-10-0-139-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "19313"
    uid: 764e918f-bd4d-489a-9eb9-1f0c1c1afcdf
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:27:19Z"
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.245717ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 2.338875ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 2.510592ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:39:19Z"
    - latency: 2.490804ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:38:19Z"
    - latency: 2.393849ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:37:19Z"
    - latency: 2.120437ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:36:19Z"
    - latency: 2.286867ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:35:19Z"
    - latency: 2.755262ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:34:19Z"
    - latency: 2.437942ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:33:19Z"
    - latency: 2.093177ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T14:20:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-223.ec2.internal
      uid: bfb02dd5-4fa7-4f41-bed1-984d1e6d1421
    resourceVersion: "20544"
    uid: 1415d887-8b53-4122-b4ed-7a1f6a1aa283
  spec:
    sourcePod: network-check-source-7d88cb55d8-4fqqw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T14:26:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 807.071µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:44:19Z"
    - latency: 1.857242ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:44:19Z"
    - latency: 914.797µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:43:19Z"
    - latency: 1.628674ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:43:19Z"
    - latency: 5.503789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:42:19Z"
    - latency: 1.889326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:42:19Z"
    - latency: 862.985µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 1.66806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:41:19Z"
    - latency: 810.559µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T14:40:19Z"
    - latency: 1.615574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T14:40:19Z"
kind: List
metadata:
  resourceVersion: ""