apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32539"
    uid: 236c1b21-7ea2-41f8-91cd-153de5536f50
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 1.365008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 1.075985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 1.214363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 1.188263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 1.199748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:40Z"
    - latency: 883.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:40Z"
    - latency: 1.025232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:40Z"
    - latency: 1.100887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:40Z"
    - latency: 1.379991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32541"
    uid: 83a73773-eea2-45f7-a17f-9a58682ed3ac
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:40Z"
      message: 'load-balancer-api-external: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.117897ms
      message: 'load-balancer-api-external: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 9.550029ms
      message: 'load-balancer-api-external: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 5.056921ms
      message: 'load-balancer-api-external: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 9.912318ms
      message: 'load-balancer-api-external: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 3.687693ms
      message: 'load-balancer-api-external: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 8.896467ms
      message: 'load-balancer-api-external: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 4.530748ms
      message: 'load-balancer-api-external: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 7.77593ms
      message: 'load-balancer-api-external: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 4.026719ms
      message: 'load-balancer-api-external: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 8.188927ms
      message: 'load-balancer-api-external: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32540"
    uid: 0934e312-c5f3-4a3b-82bb-6c69ab574fd9
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:40Z"
      message: 'load-balancer-api-internal: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.069625ms
      message: 'load-balancer-api-internal: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 9.629804ms
      message: 'load-balancer-api-internal: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 5.030454ms
      message: 'load-balancer-api-internal: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 9.877829ms
      message: 'load-balancer-api-internal: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 3.725702ms
      message: 'load-balancer-api-internal: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 8.814054ms
      message: 'load-balancer-api-internal: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 4.543589ms
      message: 'load-balancer-api-internal: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 7.735455ms
      message: 'load-balancer-api-internal: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 4.414296ms
      message: 'load-balancer-api-internal: tcp connection to a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 8.256885ms
      message: 'load-balancer-api-internal: resolved host name a0f88ea707a264094a6e0af88aeb4113-0b2550c0b6aded0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-network-check-target-ip-10-0-128-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32536"
    uid: f1eb3fe9-64f6-4120-a898-9d9e085b844e
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:40Z"
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.482884ms
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 1.517844ms
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 898.743µs
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 959.854µs
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 879.417µs
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 1.016826ms
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:40Z"
    - latency: 1.134686ms
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:40Z"
    - latency: 939.815µs
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:40Z"
    - latency: 772.793µs
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:40Z"
    - latency: 1.019648ms
      message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-network-check-target-ip-10-0-132-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32537"
    uid: 429af517-36b9-49c6-802d-5e9e6b3f3f76
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:40Z"
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.54191ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 2.337624ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 2.281399ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 2.02194ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 2.342479ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 2.291296ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:40Z"
    - latency: 2.176008ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:40Z"
    - latency: 2.095422ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:40Z"
    - latency: 2.050332ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:40Z"
    - latency: 2.443207ms
      message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-network-check-target-ip-10-0-136-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32535"
    uid: b8119b3c-d1cc-4e84-ba05-f46d5dffd82b
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:40Z"
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.360849ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 2.062977ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 2.300877ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 2.457189ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 2.126271ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 2.226211ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:40Z"
    - latency: 2.126477ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:40Z"
    - latency: 2.147755ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:40Z"
    - latency: 2.125578ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:40Z"
    - latency: 2.339809ms
      message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-17.ec2.internal
      uid: 87b18cdf-050b-442e-8f69-009a968862c1
    resourceVersion: "32538"
    uid: d5821af7-e481-4f5c-bfba-b269d20abefd
  spec:
    sourcePod: network-check-source-6f8b768455-2krvv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.188µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 2.409923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:02:40Z"
    - latency: 1.13434ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 1.912461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:01:40Z"
    - latency: 1.051975ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 1.868906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:00:40Z"
    - latency: 1.15592ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 1.836293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:59:40Z"
    - latency: 979.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:40Z"
    - latency: 1.685127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:58:40Z"
kind: List
metadata:
  resourceVersion: ""