apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "39177"
    uid: 49d2c640-c1a9-4e7a-b489-3c8c36b3631a
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:34:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 1.071251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:22:46Z"
    - latency: 702.516µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:21:46Z"
    - latency: 981.551µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:20:46Z"
    - latency: 923.005µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:19:46Z"
    - latency: 1.125634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:18:46Z"
    - latency: 1.236415ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:17:46Z"
    - latency: 1.141461ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:16:46Z"
    - latency: 1.213187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:15:46Z"
    - latency: 1.053709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:14:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "41389"
    uid: bed28346-8aae-4416-9542-1dc5747260a3
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:33:46Z"
      message: 'load-balancer-api-external: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.106924ms
      message: 'load-balancer-api-external: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:27:46Z"
    - latency: 7.033833ms
      message: 'load-balancer-api-external: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:27:46Z"
    - latency: 4.576084ms
      message: 'load-balancer-api-external: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:26:46Z"
    - latency: 7.182162ms
      message: 'load-balancer-api-external: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:26:46Z"
    - latency: 4.754469ms
      message: 'load-balancer-api-external: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:25:46Z"
    - latency: 9.793364ms
      message: 'load-balancer-api-external: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:25:46Z"
    - latency: 5.427382ms
      message: 'load-balancer-api-external: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:24:46Z"
    - latency: 7.9152ms
      message: 'load-balancer-api-external: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:24:46Z"
    - latency: 4.560372ms
      message: 'load-balancer-api-external: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 6.705345ms
      message: 'load-balancer-api-external: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:23:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "41390"
    uid: 280217c8-3fb8-47fa-8d72-b32faf5bffa7
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:33:46Z"
      message: 'load-balancer-api-internal: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.064071ms
      message: 'load-balancer-api-internal: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:27:46Z"
    - latency: 7.058775ms
      message: 'load-balancer-api-internal: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:27:46Z"
    - latency: 3.729387ms
      message: 'load-balancer-api-internal: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:26:46Z"
    - latency: 7.127663ms
      message: 'load-balancer-api-internal: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:26:46Z"
    - latency: 5.108835ms
      message: 'load-balancer-api-internal: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:25:46Z"
    - latency: 9.966261ms
      message: 'load-balancer-api-internal: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:25:46Z"
    - latency: 5.461789ms
      message: 'load-balancer-api-internal: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:24:46Z"
    - latency: 7.828841ms
      message: 'load-balancer-api-internal: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:24:46Z"
    - latency: 4.783177ms
      message: 'load-balancer-api-internal: tcp connection to a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 6.606729ms
      message: 'load-balancer-api-internal: resolved host name a7f794fcb8b2c4ec3b77ccc5e7557ff1-2ccbaf4af5715868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:23:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-network-check-target-ip-10-0-128-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "39174"
    uid: 65a96a85-abdc-462d-b774-5ddda95c2469
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:34:46Z"
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.095µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 1.378747ms
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:22:46Z"
    - latency: 801.942µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:21:46Z"
    - latency: 902.374µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:20:46Z"
    - latency: 879.807µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:19:46Z"
    - latency: 869.375µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:18:46Z"
    - latency: 875.058µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:17:46Z"
    - latency: 776.501µs
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:16:46Z"
    - latency: 1.064344ms
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:15:46Z"
    - latency: 1.426981ms
      message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:14:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-network-check-target-ip-10-0-129-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "39175"
    uid: bb8f1f11-0a4d-40d3-90d1-6f9bc1574573
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:34:46Z"
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.943061ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 1.812781ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:22:46Z"
    - latency: 1.981335ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:21:46Z"
    - latency: 1.734605ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:20:46Z"
    - latency: 2.000425ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:19:46Z"
    - latency: 1.900318ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:18:46Z"
    - latency: 1.800358ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:17:46Z"
    - latency: 1.872672ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:16:46Z"
    - latency: 1.849767ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:15:46Z"
    - latency: 1.945283ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:14:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-network-check-target-ip-10-0-143-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "39176"
    uid: 619edb1f-b6c6-45f1-8681-71db1202269a
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:34:46Z"
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264266ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 2.220293ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:22:46Z"
    - latency: 2.155188ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:21:46Z"
    - latency: 2.321882ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:20:46Z"
    - latency: 2.304994ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:19:46Z"
    - latency: 2.151005ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:18:46Z"
    - latency: 2.14155ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:17:46Z"
    - latency: 2.119676ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:16:46Z"
    - latency: 2.075781ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:15:46Z"
    - latency: 2.197623ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:14:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-36.ec2.internal
      uid: b1037e00-ca8d-4342-8d5e-cf81b7e134f8
    resourceVersion: "41386"
    uid: 1c873483-91d7-4f5e-bc76-4f1c156be4ab
  spec:
    sourcePod: network-check-source-8894fc9bd-rt2p5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:33:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 711.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:27:46Z"
    - latency: 1.840586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:27:46Z"
    - latency: 1.19566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:26:46Z"
    - latency: 1.516938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:26:46Z"
    - latency: 1.075657ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:25:46Z"
    - latency: 1.663855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:25:46Z"
    - latency: 995.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:24:46Z"
    - latency: 1.68675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:24:46Z"
    - latency: 1.133358ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T15:23:46Z"
    - latency: 1.739746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T15:23:46Z"
kind: List
metadata:
  resourceVersion: ""