apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "44578"
    uid: 60afa873-eba8-4588-9401-d8bcc0e90f5f
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:01:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:22:35Z"
    - latency: 970.246µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:21:35Z"
    - latency: 1.666258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:20:35Z"
    - latency: 982.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:19:35Z"
    - latency: 1.389967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 1.256684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 1.434306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 1.015142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 1.011937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 912.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:13:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "40357"
    uid: 31256956-09c5-4b7f-a4a8-6f1407d7a5af
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:00:36Z"
      message: 'load-balancer-api-external: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.865668ms
      message: 'load-balancer-api-external: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 8.010307ms
      message: 'load-balancer-api-external: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 4.415119ms
      message: 'load-balancer-api-external: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 7.894521ms
      message: 'load-balancer-api-external: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 4.307037ms
      message: 'load-balancer-api-external: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 6.93464ms
      message: 'load-balancer-api-external: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 5.429204ms
      message: 'load-balancer-api-external: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 7.562084ms
      message: 'load-balancer-api-external: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 9.153191ms
      message: 'load-balancer-api-external: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 7.276759ms
      message: 'load-balancer-api-external: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:14:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "40356"
    uid: 49b9c5d8-b7cf-496f-84d2-8f4943fc9bc5
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:00:36Z"
      message: 'load-balancer-api-internal: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.594773ms
      message: 'load-balancer-api-internal: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 7.855211ms
      message: 'load-balancer-api-internal: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 4.42913ms
      message: 'load-balancer-api-internal: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 7.855833ms
      message: 'load-balancer-api-internal: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 9.533716ms
      message: 'load-balancer-api-internal: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 6.968035ms
      message: 'load-balancer-api-internal: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 5.454678ms
      message: 'load-balancer-api-internal: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 7.630866ms
      message: 'load-balancer-api-internal: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 3.330737ms
      message: 'load-balancer-api-internal: tcp connection to a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 7.224422ms
      message: 'load-balancer-api-internal: resolved host name a71ad34db42754948a1947b6eb282e85-54038ae2eeee21b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:14:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-network-check-target-ip-10-0-128-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "44577"
    uid: 8e288b54-5f2c-46e4-bfb1-ff1cbac21119
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:01:35Z"
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.037389ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:22:35Z"
    - latency: 2.087496ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:21:35Z"
    - latency: 2.851445ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:20:35Z"
    - latency: 2.216132ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:19:35Z"
    - latency: 2.30001ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 1.628836ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 2.027335ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 2.001656ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 2.149189ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 1.954525ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:13:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-network-check-target-ip-10-0-133-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "44576"
    uid: eb75e7ae-350a-4384-ae43-76d4b40820bf
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:01:35Z"
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.019195ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:22:35Z"
    - latency: 1.725532ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:21:35Z"
    - latency: 1.942734ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:20:35Z"
    - latency: 1.669355ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:19:35Z"
    - latency: 1.993889ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 2.071719ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 1.83934ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 1.528206ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 1.845979ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 1.616203ms
      message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:13:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-network-check-target-ip-10-0-135-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "44575"
    uid: 68d3d6ca-c7ee-4ee0-a187-d852a4128c12
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:01:35Z"
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.756µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:22:35Z"
    - latency: 809.724µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:21:35Z"
    - latency: 2.188614ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:20:35Z"
    - latency: 709.813µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:19:35Z"
    - latency: 957.61µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 967.488µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 1.414277ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 1.02721ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 849.582µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 804.258µs
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:13:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-11T20:54:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-190-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-190.ec2.internal
      uid: 0fd1a0d9-30a3-401e-b97a-3bdf1f85b7b7
    resourceVersion: "40355"
    uid: 76b0558c-f877-49e8-8c41-6e094729f009
  spec:
    sourcePod: network-check-source-6859b67c86-hzqqm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-11T21:00:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127111ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 1.715803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:18:35Z"
    - latency: 756.082µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 1.919817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:17:35Z"
    - latency: 826.22µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 1.765479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:16:35Z"
    - latency: 854.662µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 1.95363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:15:35Z"
    - latency: 1.091337ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-11T21:14:35Z"
    - latency: 1.663254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-11T21:14:35Z"
kind: List
metadata:
  resourceVersion: ""