apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "81189"
    uid: 6f348e21-d2bf-4d85-9e28-9059b1ce38b2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:36:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 999.142µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 773.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:30:42Z"
    - latency: 1.018112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:29:42Z"
    - latency: 926.159µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:28:42Z"
    - latency: 1.279709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:27:42Z"
    - latency: 1.023779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:26:42Z"
    - latency: 1.000136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:25:42Z"
    - latency: 918.163µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:24:42Z"
    - latency: 1.099295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:23:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "84778"
    uid: 7db790ec-3fac-4bb5-a15c-8e4c34547142
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:35:42Z"
      message: 'load-balancer-api-external: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.07064ms
      message: 'load-balancer-api-external: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:35:42Z"
    - latency: 6.661376ms
      message: 'load-balancer-api-external: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:35:42Z"
    - latency: 5.093121ms
      message: 'load-balancer-api-external: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:34:42Z"
    - latency: 8.136332ms
      message: 'load-balancer-api-external: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:34:42Z"
    - latency: 3.979813ms
      message: 'load-balancer-api-external: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:33:42Z"
    - latency: 7.724106ms
      message: 'load-balancer-api-external: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:33:42Z"
    - latency: 4.617052ms
      message: 'load-balancer-api-external: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 7.429025ms
      message: 'load-balancer-api-external: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 4.892865ms
      message: 'load-balancer-api-external: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 8.029914ms
      message: 'load-balancer-api-external: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:31:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "84779"
    uid: 4672c1a1-7ff8-4f9a-8654-f3ec96f2a267
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:35:42Z"
      message: 'load-balancer-api-internal: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.059439ms
      message: 'load-balancer-api-internal: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:35:42Z"
    - latency: 6.722781ms
      message: 'load-balancer-api-internal: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:35:42Z"
    - latency: 5.079132ms
      message: 'load-balancer-api-internal: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:34:42Z"
    - latency: 8.211457ms
      message: 'load-balancer-api-internal: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:34:42Z"
    - latency: 5.323587ms
      message: 'load-balancer-api-internal: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:33:42Z"
    - latency: 7.658285ms
      message: 'load-balancer-api-internal: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:33:42Z"
    - latency: 4.732819ms
      message: 'load-balancer-api-internal: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 7.493058ms
      message: 'load-balancer-api-internal: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 5.577444ms
      message: 'load-balancer-api-internal: tcp connection to a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 7.981731ms
      message: 'load-balancer-api-internal: resolved host name a4de2e04059924ff0b7e070f4e885956-7656aba196384072.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:31:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-130-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "81186"
    uid: d0817c7a-ee39-44da-b793-bf21e1a1a533
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:36:42Z"
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.336µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 1.632962ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 1.332267ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:30:42Z"
    - latency: 1.174415ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:29:42Z"
    - latency: 1.191138ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:28:42Z"
    - latency: 988.829µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:27:42Z"
    - latency: 1.595907ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:26:42Z"
    - latency: 1.022147ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:25:42Z"
    - latency: 942.657µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:24:42Z"
    - latency: 1.658861ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:23:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-134-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "81187"
    uid: 3909b2da-0a75-4eff-ae68-283400ef19dc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:36:42Z"
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.009571ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 2.346771ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 2.311492ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:30:42Z"
    - latency: 2.249969ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:29:42Z"
    - latency: 2.333502ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:28:42Z"
    - latency: 2.009006ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:27:42Z"
    - latency: 2.299422ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:26:42Z"
    - latency: 2.196989ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:25:42Z"
    - latency: 2.459233ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:24:42Z"
    - latency: 2.588057ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:23:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-137-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "81188"
    uid: 0b83c541-a1d4-4e74-8bed-a6444d74981b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:36:42Z"
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.620016ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 2.212406ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 1.759455ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:30:42Z"
    - latency: 2.383676ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:29:42Z"
    - latency: 2.201752ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:28:42Z"
    - latency: 2.232261ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:27:42Z"
    - latency: 2.272999ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:26:42Z"
    - latency: 2.15214ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:25:42Z"
    - latency: 2.235768ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:24:42Z"
    - latency: 2.527741ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:23:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T16:29:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: a7eafff8-3379-45bf-b9e0-0294a729fd45
    resourceVersion: "84777"
    uid: 294ae93e-6675-4895-b516-3c36e12c818b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c44fh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T16:35:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050502ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:35:42Z"
    - latency: 1.695407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:35:42Z"
    - latency: 938.352µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:34:42Z"
    - latency: 2.899449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:34:42Z"
    - latency: 805.083µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:33:42Z"
    - latency: 2.000297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:33:42Z"
    - latency: 864.349µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 1.743479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:32:42Z"
    - latency: 892.842µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:31:42Z"
    - latency: 1.744417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:31:42Z"
kind: List
metadata:
  resourceVersion: ""