apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "67901"
    uid: 482d152d-999b-4206-98c6-b586e3f7605e
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:16:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.296582ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 1.487578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 1.183106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 2.90214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 1.17272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:40:25Z"
    - latency: 909.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:39:25Z"
    - latency: 1.131382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:38:25Z"
    - latency: 1.213752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:37:25Z"
    - latency: 980.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:36:25Z"
    - latency: 1.033862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "68901"
    uid: 28ced5bc-c2fd-46f4-986d-742836f88dcc
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:15:25Z"
      message: 'load-balancer-api-external: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.094774ms
      message: 'load-balancer-api-external: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:45:25Z"
    - latency: 9.541429ms
      message: 'load-balancer-api-external: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:45:25Z"
    - latency: 4.250436ms
      message: 'load-balancer-api-external: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 8.767544ms
      message: 'load-balancer-api-external: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 5.807704ms
      message: 'load-balancer-api-external: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 9.534604ms
      message: 'load-balancer-api-external: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 3.732853ms
      message: 'load-balancer-api-external: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 8.836837ms
      message: 'load-balancer-api-external: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 3.754537ms
      message: 'load-balancer-api-external: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 11.028192ms
      message: 'load-balancer-api-external: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:41:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "68900"
    uid: 314ace27-4e3b-4e7f-a97b-c8d85d781062
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:15:25Z"
      message: 'load-balancer-api-internal: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.097577ms
      message: 'load-balancer-api-internal: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:45:25Z"
    - latency: 9.443432ms
      message: 'load-balancer-api-internal: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:45:25Z"
    - latency: 4.221884ms
      message: 'load-balancer-api-internal: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 8.715925ms
      message: 'load-balancer-api-internal: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 5.711457ms
      message: 'load-balancer-api-internal: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 9.588327ms
      message: 'load-balancer-api-internal: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 3.76232ms
      message: 'load-balancer-api-internal: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 8.889729ms
      message: 'load-balancer-api-internal: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 10.646316ms
      message: 'load-balancer-api-internal: tcp connection to aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 11.246288ms
      message: 'load-balancer-api-internal: resolved host name aacc8d01d92fa4908b7d04ec258c1f25-441b492656368081.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:41:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-network-check-target-ip-10-0-134-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "67899"
    uid: 03f4a9fa-7f27-4e90-8e97-adecc0b9c162
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:16:25Z"
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.33454ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 2.232068ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 1.979891ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 3.253327ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 2.286369ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:40:25Z"
    - latency: 2.613835ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:39:25Z"
    - latency: 2.14886ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:38:25Z"
    - latency: 2.042419ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:37:25Z"
    - latency: 2.25677ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:36:25Z"
    - latency: 2.042072ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-network-check-target-ip-10-0-138-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "67898"
    uid: 80830817-4c1b-4d6f-9663-d94a989e9694
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:16:25Z"
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.046026ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 2.012927ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 1.89997ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 3.708626ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 2.130036ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:40:25Z"
    - latency: 2.197024ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:39:25Z"
    - latency: 2.113058ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:38:25Z"
    - latency: 1.961971ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:37:25Z"
    - latency: 1.941821ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:36:25Z"
    - latency: 1.951755ms
      message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-network-check-target-ip-10-0-140-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "67900"
    uid: 5a65249c-764e-420d-bcc9-2a4780a97688
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:16:25Z"
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.576328ms
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 1.551775ms
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 863.326µs
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 1.861767ms
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 1.364787ms
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:40:25Z"
    - latency: 1.038614ms
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:39:25Z"
    - latency: 1.33287ms
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:38:25Z"
    - latency: 829.539µs
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:37:25Z"
    - latency: 863.474µs
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:36:25Z"
    - latency: 934.709µs
      message: 'network-check-target-ip-10-0-140-71: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-71-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-71.ec2.internal
      uid: cc7b289b-243b-4e35-bef7-f51d77089fb8
    resourceVersion: "68899"
    uid: 4495088b-4680-4bf7-b921-3e8379bbbb2f
  spec:
    sourcePod: network-check-source-6f8b768455-7n9hs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:15:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148516ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:45:25Z"
    - latency: 2.369016ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:45:25Z"
    - latency: 1.365627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 1.673448ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:44:25Z"
    - latency: 841.21µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 2.485782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:43:25Z"
    - latency: 939.9µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 1.8911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:42:25Z"
    - latency: 923.643µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T12:41:25Z"
    - latency: 3.773679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T12:41:25Z"
kind: List
metadata:
  resourceVersion: ""