apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "56036"
    uid: 1df11edf-988b-43ee-bff5-a3ce9ed1d782
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:42:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.183263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 1.41445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 1.186658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 1.068625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 1.08746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:26Z"
    - latency: 871.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:05:26Z"
    - latency: 864.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:04:26Z"
    - latency: 901.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:03:26Z"
    - latency: 1.324901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:26Z"
    - latency: 872.138µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "57153"
    uid: 730f2943-99b9-436f-9333-71c577c9f0ae
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:41:26Z"
      message: 'load-balancer-api-external: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.927166ms
      message: 'load-balancer-api-external: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:26Z"
    - latency: 6.898157ms
      message: 'load-balancer-api-external: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:11:26Z"
    - latency: 3.960963ms
      message: 'load-balancer-api-external: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 6.934121ms
      message: 'load-balancer-api-external: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 3.513386ms
      message: 'load-balancer-api-external: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 7.578175ms
      message: 'load-balancer-api-external: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 5.212238ms
      message: 'load-balancer-api-external: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 8.791657ms
      message: 'load-balancer-api-external: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 4.126636ms
      message: 'load-balancer-api-external: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 9.734914ms
      message: 'load-balancer-api-external: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "57154"
    uid: be36d4cb-93b1-4b07-bb74-54c85d8f310c
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:41:26Z"
      message: 'load-balancer-api-internal: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.876446ms
      message: 'load-balancer-api-internal: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:26Z"
    - latency: 6.929358ms
      message: 'load-balancer-api-internal: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:11:26Z"
    - latency: 3.094492ms
      message: 'load-balancer-api-internal: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 6.846531ms
      message: 'load-balancer-api-internal: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 3.523141ms
      message: 'load-balancer-api-internal: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 7.548608ms
      message: 'load-balancer-api-internal: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 3.687731ms
      message: 'load-balancer-api-internal: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 8.760185ms
      message: 'load-balancer-api-internal: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 4.135724ms
      message: 'load-balancer-api-internal: tcp connection to a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 9.686831ms
      message: 'load-balancer-api-internal: resolved host name a2b932b5cd22d4c5e88d210c076d7dda-84df0612f1114fc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-network-check-target-ip-10-0-139-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "56035"
    uid: b671913b-65cc-45ff-b117-fe96a8f6e576
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:42:26Z"
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.738595ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 2.063467ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 2.025424ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 1.988217ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 2.189728ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:26Z"
    - latency: 2.027064ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:05:26Z"
    - latency: 2.181916ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:04:26Z"
    - latency: 1.903708ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:03:26Z"
    - latency: 1.884905ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:26Z"
    - latency: 1.97984ms
      message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-network-check-target-ip-10-0-140-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "56034"
    uid: 16f1d840-31a7-4a1c-b5de-0a719eb067df
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:42:26Z"
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.89529ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 2.128953ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 2.199329ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 2.220547ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 2.192811ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:26Z"
    - latency: 2.191069ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:05:26Z"
    - latency: 1.837531ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:04:26Z"
    - latency: 1.958602ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:03:26Z"
    - latency: 1.993218ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:26Z"
    - latency: 2.287297ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-network-check-target-ip-10-0-143-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "56033"
    uid: 1198b1a9-ebe3-46e8-9582-cd34bf233013
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:42:26Z"
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.073µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 765.314µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 751.279µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 988.487µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 816.773µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:26Z"
    - latency: 1.375921ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:05:26Z"
    - latency: 972.372µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:04:26Z"
    - latency: 933.13µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:03:26Z"
    - latency: 849.487µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:26Z"
    - latency: 923.174µs
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-133.ec2.internal
      uid: ccd02cde-3b02-4e34-b239-7ae2e06ea93f
    resourceVersion: "57152"
    uid: 35509cd9-c5b7-4e0b-9cb6-39737a8ed5b6
  spec:
    sourcePod: network-check-source-869dcfcdcd-82kr6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:41:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:26Z"
    - latency: 1.819535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:11:26Z"
    - latency: 789.244µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 1.646702ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:10:26Z"
    - latency: 820.552µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 2.110041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:09:26Z"
    - latency: 898.646µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 1.652492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:08:26Z"
    - latency: 861.269µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:26Z"
    - latency: 2.018837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:07:26Z"
kind: List
metadata:
  resourceVersion: ""