apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32757"
    uid: 1527530b-678b-490a-862b-877f775044f7
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:06:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 1.602249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 1.064437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 1.265848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 996.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 961.269µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:36:29Z"
    - latency: 844.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:35:29Z"
    - latency: 1.164607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:34:29Z"
    - latency: 994.742µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:33:29Z"
    - latency: 1.176208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:32:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32758"
    uid: 32941c1f-644d-450d-a8cb-b38de786d9c8
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:05:29Z"
      message: 'load-balancer-api-external: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.049727ms
      message: 'load-balancer-api-external: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 10.327637ms
      message: 'load-balancer-api-external: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 4.999542ms
      message: 'load-balancer-api-external: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 9.665095ms
      message: 'load-balancer-api-external: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 5.051439ms
      message: 'load-balancer-api-external: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 8.499983ms
      message: 'load-balancer-api-external: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 4.557565ms
      message: 'load-balancer-api-external: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 8.935543ms
      message: 'load-balancer-api-external: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 5.123319ms
      message: 'load-balancer-api-external: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 8.961291ms
      message: 'load-balancer-api-external: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32759"
    uid: f0087aa3-3fc1-478d-b83c-7f513dc2cede
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:05:29Z"
      message: 'load-balancer-api-internal: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045132ms
      message: 'load-balancer-api-internal: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 10.235418ms
      message: 'load-balancer-api-internal: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 4.454281ms
      message: 'load-balancer-api-internal: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 9.673479ms
      message: 'load-balancer-api-internal: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 5.028051ms
      message: 'load-balancer-api-internal: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 8.459408ms
      message: 'load-balancer-api-internal: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 4.439011ms
      message: 'load-balancer-api-internal: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 8.955858ms
      message: 'load-balancer-api-internal: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 5.181984ms
      message: 'load-balancer-api-internal: tcp connection to a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 8.897201ms
      message: 'load-balancer-api-internal: resolved host name a7d519f49ab224fcf8105e3353c948b3-0621bf4e2e22275c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-network-check-target-ip-10-0-132-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32755"
    uid: bf4376d9-8d65-4f13-a44c-52fd04336021
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:06:29Z"
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.550106ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 2.60594ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 2.25704ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 2.317379ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 2.203317ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 2.576698ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:36:29Z"
    - latency: 2.285733ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:35:29Z"
    - latency: 2.433695ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:34:29Z"
    - latency: 2.51739ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:33:29Z"
    - latency: 2.355315ms
      message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:32:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-network-check-target-ip-10-0-142-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32754"
    uid: 838c6144-16e6-404f-8d28-73431dd8d0f1
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:06:29Z"
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.199901ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 2.886194ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 2.337073ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 2.49205ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 2.241102ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 2.435211ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:36:29Z"
    - latency: 2.087483ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:35:29Z"
    - latency: 2.407806ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:34:29Z"
    - latency: 2.50609ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:33:29Z"
    - latency: 2.411547ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:32:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-network-check-target-ip-10-0-142-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32753"
    uid: eea4b81d-32c8-4061-bd65-422d220be856
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:06:29Z"
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.064µs
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 1.898253ms
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 1.1842ms
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 922.227µs
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 1.309549ms
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 1.751429ms
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:36:29Z"
    - latency: 964.309µs
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:35:29Z"
    - latency: 904.794µs
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:34:29Z"
    - latency: 1.370266ms
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:33:29Z"
    - latency: 988.741µs
      message: 'network-check-target-ip-10-0-142-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:32:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:59:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-193-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-193.ec2.internal
      uid: 9e323525-5c1b-4efc-bd8a-9c7ad0d641b2
    resourceVersion: "32756"
    uid: fa5a4151-498f-4a1a-bb5e-8864e8c55d90
  spec:
    sourcePod: network-check-source-989f8b8dc-hlx45
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:05:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 1.771619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:41:29Z"
    - latency: 892.454µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 1.810728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:40:29Z"
    - latency: 1.182534ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 1.681453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:39:29Z"
    - latency: 1.655428ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 1.728252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:38:29Z"
    - latency: 939.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:37:29Z"
    - latency: 2.384867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:37:29Z"
kind: List
metadata:
  resourceVersion: ""