apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "28118"
    uid: ee56dba1-7058-4dc6-8d4a-0c52395e87b7
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:57:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:12Z"
    - latency: 965.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:12Z"
    - latency: 971.64µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 1.106137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 1.626399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 876.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 793.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 985.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:12Z"
    - latency: 967.083µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:12Z"
    - latency: 1.030218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "26811"
    uid: 48bf25e7-b87d-486e-8fc9-9760cbc9c88d
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:56:12Z"
      message: 'load-balancer-api-external: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.128732ms
      message: 'load-balancer-api-external: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 8.015511ms
      message: 'load-balancer-api-external: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 4.985878ms
      message: 'load-balancer-api-external: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 7.294218ms
      message: 'load-balancer-api-external: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 3.71184ms
      message: 'load-balancer-api-external: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 8.973958ms
      message: 'load-balancer-api-external: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 4.852968ms
      message: 'load-balancer-api-external: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 10.462891ms
      message: 'load-balancer-api-external: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 5.347365ms
      message: 'load-balancer-api-external: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 8.379239ms
      message: 'load-balancer-api-external: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "26812"
    uid: 0c865b83-e4ba-407c-ba69-1a1d205a275c
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:56:12Z"
      message: 'load-balancer-api-internal: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.094934ms
      message: 'load-balancer-api-internal: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 8.107758ms
      message: 'load-balancer-api-internal: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 4.985993ms
      message: 'load-balancer-api-internal: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 7.237041ms
      message: 'load-balancer-api-internal: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 4.268421ms
      message: 'load-balancer-api-internal: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 9.116503ms
      message: 'load-balancer-api-internal: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 4.832478ms
      message: 'load-balancer-api-internal: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 10.616438ms
      message: 'load-balancer-api-internal: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 4.27234ms
      message: 'load-balancer-api-internal: tcp connection to a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 8.477573ms
      message: 'load-balancer-api-internal: resolved host name a85e46f4b260645779d5cb6fe46cb43a-5262e8bcaceccf23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-131-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "28115"
    uid: c0070642-16ee-436e-88ff-6cd1bbc8b425
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:57:12Z"
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026112ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:12Z"
    - latency: 881.257µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:12Z"
    - latency: 844.753µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 903.545µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 923.164µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 2.316045ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 964.072µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 1.110375ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:12Z"
    - latency: 907.156µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:12Z"
    - latency: 1.709663ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-133-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "28116"
    uid: 19ae718e-f609-4e8e-b434-0ace53fee9d3
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:57:12Z"
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.065912ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:12Z"
    - latency: 2.382386ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:12Z"
    - latency: 2.648324ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 2.276028ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 2.514472ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 1.961536ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 2.137644ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 2.232315ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:12Z"
    - latency: 2.141102ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:12Z"
    - latency: 2.554758ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-134-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "28117"
    uid: 5d597dc5-51ed-4642-9334-725d443b696d
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:57:12Z"
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.476921ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:12Z"
    - latency: 2.422848ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:12Z"
    - latency: 2.363349ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 2.696579ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 2.457071ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 2.602712ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 2.631143ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 2.360581ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:12Z"
    - latency: 2.506068ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:12Z"
    - latency: 2.392657ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:50:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: ffdb0d26-10cc-430b-9bdb-44dce97e3a63
    resourceVersion: "26810"
    uid: 2a0b436d-94cc-4e33-93ab-51255347d542
  spec:
    sourcePod: network-check-source-685456655f-2hxgn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:56:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.537µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 1.747288ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:02:12Z"
    - latency: 1.011417ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 1.668035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:01:12Z"
    - latency: 847.025µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 1.758869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:00:12Z"
    - latency: 892.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 2.285948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:59:12Z"
    - latency: 873.615µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:12Z"
    - latency: 2.200385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:58:12Z"
kind: List
metadata:
  resourceVersion: ""