apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "56396"
    uid: 1e23f916-9d22-4aba-a9fe-e132ff2e2dfa
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:27:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.802µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:55:38Z"
    - latency: 1.170987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:54:38Z"
    - latency: 1.434939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:53:38Z"
    - latency: 1.014127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:52:38Z"
    - latency: 1.087265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:51:38Z"
    - latency: 1.246843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 1.336651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 1.820739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 841.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 1.667182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "51601"
    uid: 57bdc2c6-207e-4d2b-a9bf-68fa7254fcfa
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:26:38Z"
      message: 'load-balancer-api-external: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.839341ms
      message: 'load-balancer-api-external: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 11.880811ms
      message: 'load-balancer-api-external: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 3.684176ms
      message: 'load-balancer-api-external: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 8.77187ms
      message: 'load-balancer-api-external: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 4.077151ms
      message: 'load-balancer-api-external: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 8.267408ms
      message: 'load-balancer-api-external: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 4.762634ms
      message: 'load-balancer-api-external: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 8.367866ms
      message: 'load-balancer-api-external: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 4.463387ms
      message: 'load-balancer-api-external: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
    - latency: 7.174157ms
      message: 'load-balancer-api-external: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "51602"
    uid: 7c8f92fe-9219-41f4-9f73-e50684d80ab0
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:26:38Z"
      message: 'load-balancer-api-internal: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.82659ms
      message: 'load-balancer-api-internal: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 11.848577ms
      message: 'load-balancer-api-internal: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 3.684519ms
      message: 'load-balancer-api-internal: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 8.720827ms
      message: 'load-balancer-api-internal: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 4.231946ms
      message: 'load-balancer-api-internal: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 8.251601ms
      message: 'load-balancer-api-internal: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 4.843284ms
      message: 'load-balancer-api-internal: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 8.31812ms
      message: 'load-balancer-api-internal: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 3.601841ms
      message: 'load-balancer-api-internal: tcp connection to af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
    - latency: 7.150279ms
      message: 'load-balancer-api-internal: resolved host name af357eab5b6f14769908d119d8e876e8-ad0d3663625fa87e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-network-check-target-ip-10-0-128-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "56394"
    uid: f15ff962-f767-47ca-9257-0a2eae310c37
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:27:38Z"
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.536376ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:55:38Z"
    - latency: 2.377145ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:54:38Z"
    - latency: 2.382895ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:53:38Z"
    - latency: 2.452271ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:52:38Z"
    - latency: 2.260022ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:51:38Z"
    - latency: 2.307629ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 2.282221ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 2.29278ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 2.182848ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 2.063211ms
      message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-network-check-target-ip-10-0-131-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "56393"
    uid: 272ea7f5-dbe3-46b6-bf7c-3d86f426f288
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:27:38Z"
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.588µs
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:55:38Z"
    - latency: 932.481µs
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:54:38Z"
    - latency: 1.332979ms
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:53:38Z"
    - latency: 1.284612ms
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:52:38Z"
    - latency: 1.181071ms
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:51:38Z"
    - latency: 1.442092ms
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 1.430789ms
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 828.18µs
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 838.428µs
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 1.146387ms
      message: 'network-check-target-ip-10-0-131-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-network-check-target-ip-10-0-140-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "56395"
    uid: b0f07dcd-f863-4e35-afcf-902221f60468
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:27:38Z"
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.472666ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:55:38Z"
    - latency: 2.472989ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:54:38Z"
    - latency: 2.657783ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:53:38Z"
    - latency: 2.426976ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:52:38Z"
    - latency: 2.721194ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:51:38Z"
    - latency: 2.638507ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 2.300183ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 2.451715ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 2.344372ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 1.990546ms
      message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-255.ec2.internal
      uid: f1f6c277-3a31-4575-b03b-a4a8761d39d3
    resourceVersion: "51600"
    uid: 595bf1de-6eb7-4072-af40-c72536ea152d
  spec:
    sourcePod: network-check-source-869dcfcdcd-r5wqb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:26:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120483ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 1.80747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:50:38Z"
    - latency: 1.008829ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 1.63459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:49:38Z"
    - latency: 1.161652ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 1.793989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:48:38Z"
    - latency: 740.777µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 1.560096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:47:38Z"
    - latency: 806.797µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:46:38Z"
    - latency: 1.718821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:46:38Z"
kind: List
metadata:
  resourceVersion: ""