apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "17154"
    uid: 999ecdea-3ee5-4776-b85c-81cc48ea4d73
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:52:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 935.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:18Z"
    - latency: 956.593µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:18Z"
    - latency: 1.000111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:18Z"
    - latency: 1.043465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:18Z"
    - latency: 1.272958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:18Z"
    - latency: 937.104µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:18Z"
    - latency: 1.099129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:18Z"
    - latency: 1.023588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:51:18Z"
    - latency: 973.156µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:50:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "19323"
    uid: e92993e4-a09e-475b-a6e8-9b1030d42be2
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:51:18Z"
      message: 'load-balancer-api-external: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.239899ms
      message: 'load-balancer-api-external: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:18Z"
    - latency: 8.831387ms
      message: 'load-balancer-api-external: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:03:18Z"
    - latency: 4.664ms
      message: 'load-balancer-api-external: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:18Z"
    - latency: 8.777842ms
      message: 'load-balancer-api-external: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:02:18Z"
    - latency: 3.979547ms
      message: 'load-balancer-api-external: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:18Z"
    - latency: 8.554506ms
      message: 'load-balancer-api-external: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:01:18Z"
    - latency: 5.013387ms
      message: 'load-balancer-api-external: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:18Z"
    - latency: 8.625209ms
      message: 'load-balancer-api-external: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:00:18Z"
    - latency: 6.322168ms
      message: 'load-balancer-api-external: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 8.669801ms
      message: 'load-balancer-api-external: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T02:59:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "19322"
    uid: 08999e94-8046-4805-b463-9fb8d65fde49
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:51:18Z"
      message: 'load-balancer-api-internal: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.329633ms
      message: 'load-balancer-api-internal: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:18Z"
    - latency: 8.652527ms
      message: 'load-balancer-api-internal: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:03:18Z"
    - latency: 4.661805ms
      message: 'load-balancer-api-internal: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:18Z"
    - latency: 8.726834ms
      message: 'load-balancer-api-internal: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:02:18Z"
    - latency: 4.278397ms
      message: 'load-balancer-api-internal: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:18Z"
    - latency: 8.611433ms
      message: 'load-balancer-api-internal: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:01:18Z"
    - latency: 5.03057ms
      message: 'load-balancer-api-internal: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:18Z"
    - latency: 8.546874ms
      message: 'load-balancer-api-internal: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:00:18Z"
    - latency: 6.020776ms
      message: 'load-balancer-api-internal: tcp connection to ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 8.63535ms
      message: 'load-balancer-api-internal: resolved host name ae95637bbe3a94a51ad0a56ff71b207d-6b9926fc0325a6db.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T02:59:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-ip-10-0-130-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "17152"
    uid: 40a9d239-06d5-48e3-8854-e174e790a4d0
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:52:18Z"
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37355ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 2.114398ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:18Z"
    - latency: 2.137033ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:18Z"
    - latency: 2.276624ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:18Z"
    - latency: 2.205025ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:18Z"
    - latency: 2.334821ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:18Z"
    - latency: 2.528062ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:18Z"
    - latency: 2.377066ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:18Z"
    - latency: 2.468511ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:51:18Z"
    - latency: 2.310818ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:50:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-ip-10-0-133-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "17153"
    uid: bfc1faed-b76c-4e9d-a5a6-0d52348049d1
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:52:18Z"
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.409797ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 2.01367ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:18Z"
    - latency: 2.34385ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:18Z"
    - latency: 2.258893ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:18Z"
    - latency: 2.337191ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:18Z"
    - latency: 2.240445ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:18Z"
    - latency: 2.580718ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:18Z"
    - latency: 2.41057ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:18Z"
    - latency: 2.262296ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:51:18Z"
    - latency: 2.233521ms
      message: 'network-check-target-ip-10-0-133-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:50:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-ip-10-0-137-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "17151"
    uid: fa71aadd-cdff-4c4b-86dc-db2957a26d7b
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:52:18Z"
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.3µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 1.146376ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:18Z"
    - latency: 922.709µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:18Z"
    - latency: 861.283µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:18Z"
    - latency: 1.078017ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:18Z"
    - latency: 945.441µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:18Z"
    - latency: 941.828µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:18Z"
    - latency: 1.114007ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:18Z"
    - latency: 1.28044ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:51:18Z"
    - latency: 954.521µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:50:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.ec2.internal
      uid: 35f3f3b5-60a9-4326-9cc9-3fcd66a38ebb
    resourceVersion: "19321"
    uid: c62dc72d-1071-4f89-a0ae-313258762ca5
  spec:
    sourcePod: network-check-source-7cbc45fddc-kcxhk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:51:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068646ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:18Z"
    - latency: 1.76019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:03:18Z"
    - latency: 1.114068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:18Z"
    - latency: 1.834321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:02:18Z"
    - latency: 1.24548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:18Z"
    - latency: 2.002603ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:01:18Z"
    - latency: 781.28µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:18Z"
    - latency: 2.019037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:00:18Z"
    - latency: 1.097095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:18Z"
    - latency: 1.836407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T02:59:18Z"
kind: List
metadata:
  resourceVersion: ""