apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "23385"
    uid: 7326d86e-dcb9-4205-8ffb-138fca7c22b4
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:08:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.36166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:15:55Z"
    - latency: 1.11985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:14:55Z"
    - latency: 1.138664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 1.167497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 1.7241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 1.272009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 1.187168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 1.287148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:55Z"
    - latency: 952.931µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:55Z"
    - latency: 1.001844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "22245"
    uid: 7b560514-80f7-41d7-bb91-4b55076cc3a6
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:07:55Z"
      message: 'load-balancer-api-external: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.123825ms
      message: 'load-balancer-api-external: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 8.840477ms
      message: 'load-balancer-api-external: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 4.559284ms
      message: 'load-balancer-api-external: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 9.191259ms
      message: 'load-balancer-api-external: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 4.61303ms
      message: 'load-balancer-api-external: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 9.402935ms
      message: 'load-balancer-api-external: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 4.694202ms
      message: 'load-balancer-api-external: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 9.678947ms
      message: 'load-balancer-api-external: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 6.306954ms
      message: 'load-balancer-api-external: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 9.212075ms
      message: 'load-balancer-api-external: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:09:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "22244"
    uid: 4570be22-f08b-42d4-907e-98bb18c3d5d6
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:07:55Z"
      message: 'load-balancer-api-internal: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.479547ms
      message: 'load-balancer-api-internal: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 8.623482ms
      message: 'load-balancer-api-internal: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 4.541689ms
      message: 'load-balancer-api-internal: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 9.126545ms
      message: 'load-balancer-api-internal: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 4.626354ms
      message: 'load-balancer-api-internal: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 9.321708ms
      message: 'load-balancer-api-internal: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 4.647543ms
      message: 'load-balancer-api-internal: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 9.805003ms
      message: 'load-balancer-api-internal: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 6.412006ms
      message: 'load-balancer-api-internal: tcp connection to ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 9.065457ms
      message: 'load-balancer-api-internal: resolved host name ab4b921a093394c9fab20d9d54313ffb-45f5f95fe9cd6b7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:09:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-ip-10-0-128-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "23383"
    uid: e1bc4cbe-4759-4f0f-a59b-248b9c262289
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:08:55Z"
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079071ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:15:55Z"
    - latency: 2.157373ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:14:55Z"
    - latency: 2.36631ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 2.274054ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 2.39542ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 2.395455ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 2.5336ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 2.314289ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:55Z"
    - latency: 2.457697ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:55Z"
    - latency: 2.242536ms
      message: 'network-check-target-ip-10-0-128-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-ip-10-0-131-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "23382"
    uid: b11c71e4-5eae-4071-9392-e066a139a356
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:08:55Z"
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.42µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:15:55Z"
    - latency: 1.375591ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:14:55Z"
    - latency: 1.343365ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 842.452µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 1.522937ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 955.174µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 1.123371ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 1.046872ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:55Z"
    - latency: 881.854µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:55Z"
    - latency: 1.049512ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-ip-10-0-139-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "23384"
    uid: 8b41f526-81e5-48ad-830b-5ce03d83dfb2
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:08:55Z"
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382207ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:15:55Z"
    - latency: 2.395105ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:14:55Z"
    - latency: 2.287384ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 2.375125ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 2.300627ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 2.470034ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 2.395071ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 2.269885ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:08:55Z"
    - latency: 1.934623ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:07:55Z"
    - latency: 2.385188ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:06:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:01:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 4b979638-f9ff-45e6-a912-dd457ecf6c86
    resourceVersion: "22243"
    uid: fcf90d91-b727-441b-8f61-b711750e3e69
  spec:
    sourcePod: network-check-source-869dcfcdcd-cst25
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:07:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.064868ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 1.793161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:13:55Z"
    - latency: 1.270558ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 1.725594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:12:55Z"
    - latency: 1.0014ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 2.822904ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:11:55Z"
    - latency: 1.084828ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 1.727033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:10:55Z"
    - latency: 1.459399ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:09:55Z"
    - latency: 2.172065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:09:55Z"
kind: List
metadata:
  resourceVersion: ""