apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "68401"
    uid: 169a5f5d-9f90-4cc0-8650-cb7e320aaa72
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:28:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.327086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 1.103039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 871.317µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 1.350019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 1.101501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:52:03Z"
    - latency: 1.075628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:51:03Z"
    - latency: 1.387736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:50:03Z"
    - latency: 981.854µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:49:03Z"
    - latency: 1.404381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:48:03Z"
    - latency: 1.610603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "69226"
    uid: 2e008f9a-5764-421b-8ba8-ba59be09c544
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:27:03Z"
      message: 'load-balancer-api-external: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.747497ms
      message: 'load-balancer-api-external: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:57:03Z"
    - latency: 9.979486ms
      message: 'load-balancer-api-external: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:57:03Z"
    - latency: 3.875892ms
      message: 'load-balancer-api-external: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 8.814673ms
      message: 'load-balancer-api-external: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 5.427318ms
      message: 'load-balancer-api-external: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 9.312852ms
      message: 'load-balancer-api-external: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 5.374213ms
      message: 'load-balancer-api-external: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 21.300204ms
      message: 'load-balancer-api-external: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 5.223426ms
      message: 'load-balancer-api-external: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 9.733509ms
      message: 'load-balancer-api-external: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:53:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "69225"
    uid: e0d89f89-b064-40b9-99c7-6de79b50c866
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:27:03Z"
      message: 'load-balancer-api-internal: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.803197ms
      message: 'load-balancer-api-internal: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:57:03Z"
    - latency: 10.004486ms
      message: 'load-balancer-api-internal: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:57:03Z"
    - latency: 3.910516ms
      message: 'load-balancer-api-internal: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 8.871109ms
      message: 'load-balancer-api-internal: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 5.42092ms
      message: 'load-balancer-api-internal: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 9.371578ms
      message: 'load-balancer-api-internal: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 5.347642ms
      message: 'load-balancer-api-internal: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 21.326225ms
      message: 'load-balancer-api-internal: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 5.25749ms
      message: 'load-balancer-api-internal: tcp connection to a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 9.698762ms
      message: 'load-balancer-api-internal: resolved host name a443f01f695404c89887f77e41dfa667-37a84f0e96396940.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:53:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-132-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "68400"
    uid: a31bb587-8bd1-414e-80df-a28d3f2cc0bb
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:28:03Z"
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382064ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 2.50966ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 2.256105ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 2.391894ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 2.096794ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:52:03Z"
    - latency: 2.426939ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:51:03Z"
    - latency: 2.240719ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:50:03Z"
    - latency: 2.234284ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:49:03Z"
    - latency: 2.669899ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:48:03Z"
    - latency: 2.602202ms
      message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-135-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "68398"
    uid: 03661f82-a51c-41a3-9ea4-977e76a07e12
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:28:03Z"
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.057078ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 1.020147ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 1.267221ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 1.020102ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 985.66µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:52:03Z"
    - latency: 1.040164ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:51:03Z"
    - latency: 1.178026ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:50:03Z"
    - latency: 1.063362ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:49:03Z"
    - latency: 1.605789ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:48:03Z"
    - latency: 1.616092ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-141-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "68399"
    uid: a292a846-00d0-4146-b77f-11833e9cbe4b
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:28:03Z"
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376295ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 2.515292ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 2.326648ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 2.447686ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 1.936924ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:52:03Z"
    - latency: 2.210126ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:51:03Z"
    - latency: 2.326937ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:50:03Z"
    - latency: 2.401141ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:49:03Z"
    - latency: 2.730833ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:48:03Z"
    - latency: 2.636174ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T10:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 81a6fc79-4ab1-4358-aad3-dbeb51ad51bd
    resourceVersion: "69224"
    uid: 4d041991-326e-4a03-a713-60e586eb6d32
  spec:
    sourcePod: network-check-source-6f8b768455-mlhbw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:27:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.211µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:57:03Z"
    - latency: 2.45398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:57:03Z"
    - latency: 1.117327ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 1.929789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:56:03Z"
    - latency: 1.281627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 1.849567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:55:03Z"
    - latency: 1.452791ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 1.859011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:54:03Z"
    - latency: 937.345µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:53:03Z"
    - latency: 1.815335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:53:03Z"
kind: List
metadata:
  resourceVersion: ""