apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "54197"
    uid: 3aa5f82f-117f-4ace-a3ac-deeacc914e06
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:31:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.359873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 1.036179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 1.098592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 1.120221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:49:47Z"
    - latency: 898.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:48:47Z"
    - latency: 1.124043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:47:47Z"
    - latency: 1.110323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:46:47Z"
    - latency: 1.204355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:45:47Z"
    - latency: 1.688729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:44:47Z"
    - latency: 1.174276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:43:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "55891"
    uid: b8e6495e-d5d0-4550-bef9-2277f503c76d
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:30:47Z"
      message: 'load-balancer-api-external: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.036521ms
      message: 'load-balancer-api-external: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:47Z"
    - latency: 8.564967ms
      message: 'load-balancer-api-external: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:54:47Z"
    - latency: 4.803335ms
      message: 'load-balancer-api-external: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:47Z"
    - latency: 7.139196ms
      message: 'load-balancer-api-external: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:53:47Z"
    - latency: 4.89885ms
      message: 'load-balancer-api-external: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 9.100032ms
      message: 'load-balancer-api-external: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 4.734239ms
      message: 'load-balancer-api-external: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 8.279001ms
      message: 'load-balancer-api-external: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 3.850577ms
      message: 'load-balancer-api-external: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 8.450596ms
      message: 'load-balancer-api-external: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:50:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "55890"
    uid: b5f26186-0e9f-4194-8b5d-081c25229011
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:30:47Z"
      message: 'load-balancer-api-internal: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.253826ms
      message: 'load-balancer-api-internal: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:47Z"
    - latency: 8.525858ms
      message: 'load-balancer-api-internal: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:54:47Z"
    - latency: 4.826206ms
      message: 'load-balancer-api-internal: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:47Z"
    - latency: 7.119971ms
      message: 'load-balancer-api-internal: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:53:47Z"
    - latency: 3.553877ms
      message: 'load-balancer-api-internal: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 9.141222ms
      message: 'load-balancer-api-internal: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 4.765393ms
      message: 'load-balancer-api-internal: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 8.208148ms
      message: 'load-balancer-api-internal: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 3.888393ms
      message: 'load-balancer-api-internal: tcp connection to a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 8.429003ms
      message: 'load-balancer-api-internal: resolved host name a8a1f1bfc06764de689622c4fa8a1e21-ecea5363b17d5499.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:50:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-network-check-target-ip-10-0-130-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "54196"
    uid: f833258a-7208-433f-a5d3-04d1c339cdf1
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:31:47Z"
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.541811ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 2.415957ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 2.692198ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 2.415877ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:49:47Z"
    - latency: 2.069422ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:48:47Z"
    - latency: 2.490548ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:47:47Z"
    - latency: 1.955451ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:46:47Z"
    - latency: 2.287732ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:45:47Z"
    - latency: 2.303367ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:44:47Z"
    - latency: 2.197712ms
      message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:43:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-network-check-target-ip-10-0-130-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "54195"
    uid: 1d7c0786-4186-4422-8439-36223951cf7a
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:31:47Z"
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.236996ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 2.110663ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 1.816374ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 1.843709ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:49:47Z"
    - latency: 1.720457ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:48:47Z"
    - latency: 2.154082ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:47:47Z"
    - latency: 2.04036ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:46:47Z"
    - latency: 2.172216ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:45:47Z"
    - latency: 2.03188ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:44:47Z"
    - latency: 1.734935ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:43:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-network-check-target-ip-10-0-137-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "54193"
    uid: bc95dfc4-5ce1-4b9d-9e3f-b7e3cc21be07
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:31:47Z"
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.206645ms
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 1.428969ms
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 861.25µs
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 1.074086ms
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:49:47Z"
    - latency: 1.281543ms
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:48:47Z"
    - latency: 910.448µs
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:47:47Z"
    - latency: 1.127635ms
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:46:47Z"
    - latency: 796.059µs
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:45:47Z"
    - latency: 1.066391ms
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:44:47Z"
    - latency: 836.489µs
      message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:43:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T10:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-121.ec2.internal
      uid: 64b29430-a6d8-40b0-b1a0-d30e89745531
    resourceVersion: "55889"
    uid: 8941e149-f277-42cc-9d6e-4847b6eb6df6
  spec:
    sourcePod: network-check-source-685456655f-zp6cg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T10:30:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.138µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:54:47Z"
    - latency: 1.761048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:54:47Z"
    - latency: 1.114118ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:53:47Z"
    - latency: 1.796681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:53:47Z"
    - latency: 868.122µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 1.73338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:52:47Z"
    - latency: 1.3228ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 1.940767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:51:47Z"
    - latency: 1.145181ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T10:50:47Z"
    - latency: 1.663774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T10:50:47Z"
kind: List
metadata:
  resourceVersion: ""