apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "19673"
    uid: e49e1778-4ad0-4388-8dae-aa850f6317d2
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:06:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.841839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:20:15Z"
    - latency: 1.320803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:19:15Z"
    - latency: 948.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:18:15Z"
    - latency: 1.470565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 827.57µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 1.085136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 1.040545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 1.874353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 927.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:12:15Z"
    - latency: 943.077µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:11:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "18479"
    uid: dc62a164-1070-43b3-8869-23bba4f5f1a7
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:05:15Z"
      message: 'load-balancer-api-external: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.550468ms
      message: 'load-balancer-api-external: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 9.093855ms
      message: 'load-balancer-api-external: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 3.866005ms
      message: 'load-balancer-api-external: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 9.202072ms
      message: 'load-balancer-api-external: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 4.039624ms
      message: 'load-balancer-api-external: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 7.701829ms
      message: 'load-balancer-api-external: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 3.618177ms
      message: 'load-balancer-api-external: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 8.99546ms
      message: 'load-balancer-api-external: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 2.907285ms
      message: 'load-balancer-api-external: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 9.577496ms
      message: 'load-balancer-api-external: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:13:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "18478"
    uid: a2da9bc9-c3f7-4322-ac9e-febee298034d
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:05:15Z"
      message: 'load-balancer-api-internal: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.523556ms
      message: 'load-balancer-api-internal: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 9.230427ms
      message: 'load-balancer-api-internal: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 3.868005ms
      message: 'load-balancer-api-internal: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 9.236037ms
      message: 'load-balancer-api-internal: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 4.024782ms
      message: 'load-balancer-api-internal: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 7.744565ms
      message: 'load-balancer-api-internal: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 4.995038ms
      message: 'load-balancer-api-internal: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 9.063621ms
      message: 'load-balancer-api-internal: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 4.509302ms
      message: 'load-balancer-api-internal: tcp connection to ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 9.671503ms
      message: 'load-balancer-api-internal: resolved host name ae9029d7d56c843b9857f7ebae2eeba6-19a4c20f4fe32ceb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:13:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-network-check-target-ip-10-0-131-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "19672"
    uid: 6ece8474-7592-4d03-800e-ae84a66dd30f
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:06:15Z"
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.291968ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:20:15Z"
    - latency: 2.171945ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:19:15Z"
    - latency: 1.934911ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:18:15Z"
    - latency: 2.523479ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 2.090618ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 2.300794ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 2.219675ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 2.166196ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 2.121695ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:12:15Z"
    - latency: 2.465994ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:11:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-network-check-target-ip-10-0-140-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "19671"
    uid: f35e49fe-e8b0-4b63-a1c0-6821bb1f4520
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:06:15Z"
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.003948ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:20:15Z"
    - latency: 1.896529ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:19:15Z"
    - latency: 1.995062ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:18:15Z"
    - latency: 2.080524ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 1.897419ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 1.972494ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 2.227443ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 2.208459ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 2.016357ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:12:15Z"
    - latency: 2.20137ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:11:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-network-check-target-ip-10-0-143-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "19670"
    uid: b5d33339-7c94-462a-b638-d9cea7a58833
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:06:15Z"
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.979µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:20:15Z"
    - latency: 819.55µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:19:15Z"
    - latency: 867.4µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:18:15Z"
    - latency: 1.622248ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 881.214µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 880.215µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 791.644µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 1.757132ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 874.988µs
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:12:15Z"
    - latency: 1.173874ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:11:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T11:59:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-53-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-53.ec2.internal
      uid: 49b436cb-dfeb-4866-94dc-359f170a435b
    resourceVersion: "18476"
    uid: 0a4c866e-f85e-4fd8-b4e8-753b2e71c615
  spec:
    sourcePod: network-check-source-6f8b768455-pwhnh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:05:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28876ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 2.345474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:17:15Z"
    - latency: 752.046µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 2.201672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:16:15Z"
    - latency: 950.28µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 1.924631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:15:15Z"
    - latency: 958.635µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 1.780572ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:14:15Z"
    - latency: 1.000329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:13:15Z"
    - latency: 2.169056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:13:15Z"
kind: List
metadata:
  resourceVersion: ""