apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "72998"
    uid: 8473c026-3839-44ab-b358-d2a1e3112ca6
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:25:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.388µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:07:50Z"
    - latency: 1.096921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 909.444µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 1.030745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 1.04562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 1.037626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 927.116µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:01:50Z"
    - latency: 1.711719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:00:50Z"
    - latency: 1.086443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:59:50Z"
    - latency: 992.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:58:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "70687"
    uid: 702ac2e2-f920-4744-94d9-24d768c772c4
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:24:50Z"
      message: 'load-balancer-api-external: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.676512ms
      message: 'load-balancer-api-external: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 8.159708ms
      message: 'load-balancer-api-external: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 3.895834ms
      message: 'load-balancer-api-external: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 7.455687ms
      message: 'load-balancer-api-external: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 4.979812ms
      message: 'load-balancer-api-external: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 7.645661ms
      message: 'load-balancer-api-external: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 4.814892ms
      message: 'load-balancer-api-external: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 7.304797ms
      message: 'load-balancer-api-external: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 4.420441ms
      message: 'load-balancer-api-external: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 7.099644ms
      message: 'load-balancer-api-external: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:02:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "70685"
    uid: 9b17dab0-3630-454c-97b0-d8289cb57e15
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:24:50Z"
      message: 'load-balancer-api-internal: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.626356ms
      message: 'load-balancer-api-internal: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 8.270347ms
      message: 'load-balancer-api-internal: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 3.285557ms
      message: 'load-balancer-api-internal: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 7.436862ms
      message: 'load-balancer-api-internal: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 4.488134ms
      message: 'load-balancer-api-internal: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 7.602138ms
      message: 'load-balancer-api-internal: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 4.851424ms
      message: 'load-balancer-api-internal: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 7.260162ms
      message: 'load-balancer-api-internal: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 4.40369ms
      message: 'load-balancer-api-internal: tcp connection to a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 7.106458ms
      message: 'load-balancer-api-internal: resolved host name a02c57e3f455c4c37bbbc46120e0bae4-3614e77f216703f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:02:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-network-check-target-ip-10-0-131-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "72997"
    uid: 29d2018a-173f-449b-aad0-5e2d9e37e8d0
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:25:50Z"
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.343495ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:07:50Z"
    - latency: 2.416552ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 2.567534ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 2.943647ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 2.649188ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 2.037538ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 1.759141ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:01:50Z"
    - latency: 2.273694ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:00:50Z"
    - latency: 2.621298ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:59:50Z"
    - latency: 2.301761ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:58:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-network-check-target-ip-10-0-131-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "72996"
    uid: c0fc7e09-6165-4931-b383-8058564059a8
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:25:50Z"
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272936ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:07:50Z"
    - latency: 2.524655ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 2.133896ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 2.517303ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 2.350028ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 2.252466ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 2.318712ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:01:50Z"
    - latency: 2.330051ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:00:50Z"
    - latency: 2.67761ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:59:50Z"
    - latency: 2.436781ms
      message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:58:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-network-check-target-ip-10-0-134-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "72995"
    uid: fe00a1b9-b2e3-45e8-825f-d0dd353acbae
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:25:50Z"
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035938ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:07:50Z"
    - latency: 1.116506ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 999.373µs
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 1.365935ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 1.712541ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 1.118814ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 1.165612ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:01:50Z"
    - latency: 1.032174ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:00:50Z"
    - latency: 1.003157ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:59:50Z"
    - latency: 1.299867ms
      message: 'network-check-target-ip-10-0-134-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:58:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:18:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-165.ec2.internal
      uid: b7a3787b-5011-4852-8b53-510f82b74fe6
    resourceVersion: "70684"
    uid: c2b5aedb-b6f5-49a6-a8e1-23226f07d3c6
  spec:
    sourcePod: network-check-source-7d88cb55d8-rqtjj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:24:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.68803ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 1.739274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:06:50Z"
    - latency: 1.028983ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 1.662898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:05:50Z"
    - latency: 1.228162ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 2.169454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:04:50Z"
    - latency: 1.226092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 2.210048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:03:50Z"
    - latency: 1.061852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:02:50Z"
    - latency: 2.022426ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:02:50Z"
kind: List
metadata:
  resourceVersion: ""