apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "30941"
    uid: 55e9d96b-3132-47ae-b80e-5f2d8b16461a
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:00:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.389µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:07:23Z"
    - latency: 977.714µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:06:23Z"
    - latency: 884.916µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 878.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 892.103µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 1.393202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 803.417µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 966.858µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:00:23Z"
    - latency: 1.003698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:59:23Z"
    - latency: 928.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:58:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "29398"
    uid: dd8338cd-3c7d-436a-82ca-0989c0a360c6
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:59:23Z"
      message: 'load-balancer-api-external: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.117408ms
      message: 'load-balancer-api-external: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 6.431155ms
      message: 'load-balancer-api-external: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 4.72685ms
      message: 'load-balancer-api-external: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 8.289486ms
      message: 'load-balancer-api-external: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 5.515845ms
      message: 'load-balancer-api-external: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 8.26367ms
      message: 'load-balancer-api-external: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 12.015837ms
      message: 'load-balancer-api-external: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 8.595749ms
      message: 'load-balancer-api-external: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 5.735302ms
      message: 'load-balancer-api-external: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 7.382046ms
      message: 'load-balancer-api-external: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:01:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "29399"
    uid: d0f67e39-b38e-454a-a37c-ce7ce1b482f3
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:59:23Z"
      message: 'load-balancer-api-internal: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.522309ms
      message: 'load-balancer-api-internal: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 6.370168ms
      message: 'load-balancer-api-internal: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 4.822497ms
      message: 'load-balancer-api-internal: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 8.32932ms
      message: 'load-balancer-api-internal: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 3.647645ms
      message: 'load-balancer-api-internal: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 8.311633ms
      message: 'load-balancer-api-internal: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 7.968824ms
      message: 'load-balancer-api-internal: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 8.681894ms
      message: 'load-balancer-api-internal: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 5.745382ms
      message: 'load-balancer-api-internal: tcp connection to a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 7.360831ms
      message: 'load-balancer-api-internal: resolved host name a33b717e550ad4c938c3c8629c02510c-4b2c8fc09d7783a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:01:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-network-check-target-ip-10-0-133-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "30940"
    uid: d9a77251-3f9a-464f-9e80-f4557afd99e7
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:00:23Z"
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42187ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:07:23Z"
    - latency: 2.429756ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:06:23Z"
    - latency: 2.043524ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 2.181933ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 1.796924ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 2.286829ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 2.17829ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 1.835782ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:00:23Z"
    - latency: 2.165298ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:59:23Z"
    - latency: 2.013514ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:58:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-network-check-target-ip-10-0-134-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "30939"
    uid: b9708aeb-5d9c-4db3-9385-d9b3d7acb5ce
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:00:23Z"
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.525333ms
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:07:23Z"
    - latency: 1.468669ms
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:06:23Z"
    - latency: 944.34µs
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 886.7µs
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 1.265447ms
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 1.78365ms
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 1.423765ms
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 933.569µs
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:00:23Z"
    - latency: 1.330443ms
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:59:23Z"
    - latency: 820.441µs
      message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:58:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-network-check-target-ip-10-0-140-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "30938"
    uid: 56345b04-0fc3-4622-a058-53abc78fa64c
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:00:23Z"
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.407183ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:07:23Z"
    - latency: 2.53ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:06:23Z"
    - latency: 2.345964ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 2.145981ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 2.091645ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 2.268781ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 2.530519ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 2.357556ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:00:23Z"
    - latency: 2.478942ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:59:23Z"
    - latency: 2.120723ms
      message: 'network-check-target-ip-10-0-140-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:58:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T14:53:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-32-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-32.ec2.internal
      uid: cc5c0337-3282-4915-8770-cbe8860be63d
    resourceVersion: "29397"
    uid: 482ba006-1139-48a0-a54a-b2c107e639b2
  spec:
    sourcePod: network-check-source-56d84b9f44-flj89
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:59:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.409µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 1.749431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:05:23Z"
    - latency: 729.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 1.541295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:04:23Z"
    - latency: 817.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 1.672709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:03:23Z"
    - latency: 818.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 1.551063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:02:23Z"
    - latency: 985.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:01:23Z"
    - latency: 1.609894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:01:23Z"
kind: List
metadata:
  resourceVersion: ""