apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "78438"
    uid: 3c08a4dc-6b65-4ec2-87d8-9742b1caa2ad
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:11:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.804516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T20:00:40Z"
    - latency: 1.180479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:59:40Z"
    - latency: 1.172219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 1.113396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 6.832206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 1.114394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 1.315448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 1.392335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:53:40Z"
    - latency: 1.023175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:52:40Z"
    - latency: 825.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:51:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "76530"
    uid: 0c15a4af-8a3c-4259-aeca-a47edd77b638
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:10:40Z"
      message: 'load-balancer-api-external: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.734637ms
      message: 'load-balancer-api-external: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 7.938341ms
      message: 'load-balancer-api-external: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 3.60957ms
      message: 'load-balancer-api-external: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 7.085609ms
      message: 'load-balancer-api-external: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 5.020303ms
      message: 'load-balancer-api-external: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 20.394113ms
      message: 'load-balancer-api-external: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 5.166008ms
      message: 'load-balancer-api-external: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 8.611511ms
      message: 'load-balancer-api-external: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 5.167387ms
      message: 'load-balancer-api-external: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 7.210477ms
      message: 'load-balancer-api-external: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:54:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "76531"
    uid: f9e27770-681b-4f3c-8f6b-ce7f71f9e1ae
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:10:40Z"
      message: 'load-balancer-api-internal: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.654949ms
      message: 'load-balancer-api-internal: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 7.985387ms
      message: 'load-balancer-api-internal: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 4.437851ms
      message: 'load-balancer-api-internal: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 7.004224ms
      message: 'load-balancer-api-internal: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 4.025312ms
      message: 'load-balancer-api-internal: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 19.022216ms
      message: 'load-balancer-api-internal: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 5.140664ms
      message: 'load-balancer-api-internal: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 8.561367ms
      message: 'load-balancer-api-internal: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 5.164956ms
      message: 'load-balancer-api-internal: tcp connection to a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 7.175383ms
      message: 'load-balancer-api-internal: resolved host name a3e2f79d1a7ce4bd1914c597829b977c-76ce0fd2aefa4fe8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:54:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-ip-10-0-131-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "78435"
    uid: 22905469-1c49-40b1-ad8c-6fb22f33f3b8
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:11:40Z"
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.011845ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T20:00:40Z"
    - latency: 882.276µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:59:40Z"
    - latency: 1.873815ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 1.127202ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 1.171434ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 1.582553ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 1.576051ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 1.124485ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:53:40Z"
    - latency: 1.078611ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:52:40Z"
    - latency: 942.592µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:51:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-ip-10-0-133-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "78437"
    uid: fb9eba9e-bc38-49bf-8880-f37ade01f71b
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:11:40Z"
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.685899ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T20:00:40Z"
    - latency: 2.7156ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:59:40Z"
    - latency: 2.600536ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 2.444783ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 6.443086ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 2.725011ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 2.647761ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 2.540232ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:53:40Z"
    - latency: 2.792364ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:52:40Z"
    - latency: 1.820453ms
      message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:51:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-ip-10-0-143-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "78436"
    uid: ceab0b41-d1f0-45ff-83a6-72be8600be0b
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:11:40Z"
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.629103ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T20:00:40Z"
    - latency: 2.826092ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:59:40Z"
    - latency: 2.90749ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 2.77157ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 5.258334ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 2.832456ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 3.131569ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 2.663005ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:53:40Z"
    - latency: 2.539406ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:52:40Z"
    - latency: 2.414086ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:51:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T19:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: ac25a4c5-012b-4bcd-ae08-a887c11b2343
    resourceVersion: "76529"
    uid: ded57f12-a27a-4cca-8301-5d8988697e32
  spec:
    sourcePod: network-check-source-65bdbbff45-7tfb9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T19:10:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.125058ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 1.861873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:58:40Z"
    - latency: 1.016717ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 2.11989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:57:40Z"
    - latency: 3.152678ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 11.443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:56:40Z"
    - latency: 1.280725ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 2.160013ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:55:40Z"
    - latency: 1.813364ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T19:54:40Z"
    - latency: 1.901971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T19:54:40Z"
kind: List
metadata:
  resourceVersion: ""