apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "150003"
    uid: da7653e5-3eba-4df1-aa4d-5b3b3cf22001
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.03965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 1.314813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 1.046826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:48Z"
    - latency: 1.313185ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:48Z"
    - latency: 940.742µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:48Z"
    - latency: 1.324929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:48Z"
    - latency: 1.589967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:48Z"
    - latency: 1.205287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:48Z"
    - latency: 1.403905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:48Z"
    - latency: 1.031382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "153275"
    uid: a2f81e97-147f-40bd-97ff-477dfa62c3f3
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:39:48Z"
      message: 'load-balancer-api-external: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.15592ms
      message: 'load-balancer-api-external: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:39:48Z"
    - latency: 7.275226ms
      message: 'load-balancer-api-external: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:39:48Z"
    - latency: 15.811773ms
      message: 'load-balancer-api-external: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:38:48Z"
    - latency: 13.68798ms
      message: 'load-balancer-api-external: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:38:48Z"
    - latency: 17.589283ms
      message: 'load-balancer-api-external: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:37:48Z"
    - latency: 8.138347ms
      message: 'load-balancer-api-external: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:37:48Z"
    - latency: 15.161918ms
      message: 'load-balancer-api-external: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 6.376762ms
      message: 'load-balancer-api-external: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 16.616463ms
      message: 'load-balancer-api-external: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 7.167182ms
      message: 'load-balancer-api-external: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:35:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "153276"
    uid: 0d3f3846-2dc9-4cc6-a6d0-ed4d249b6a2d
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:39:48Z"
      message: 'load-balancer-api-internal: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.139951ms
      message: 'load-balancer-api-internal: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:39:48Z"
    - latency: 7.22837ms
      message: 'load-balancer-api-internal: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:39:48Z"
    - latency: 16.746752ms
      message: 'load-balancer-api-internal: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:38:48Z"
    - latency: 13.454461ms
      message: 'load-balancer-api-internal: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:38:48Z"
    - latency: 17.07804ms
      message: 'load-balancer-api-internal: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:37:48Z"
    - latency: 8.183011ms
      message: 'load-balancer-api-internal: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:37:48Z"
    - latency: 15.118052ms
      message: 'load-balancer-api-internal: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 6.404538ms
      message: 'load-balancer-api-internal: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 17.356801ms
      message: 'load-balancer-api-internal: tcp connection to a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 7.12441ms
      message: 'load-balancer-api-internal: resolved host name a5b287ab80c7c42d19d760fc597948b5-039d40c1d7e6677c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:35:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-network-check-target-ip-10-0-136-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "150000"
    uid: 903fec97-c53d-4386-bb34-c55da9e10c81
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:48Z"
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.205µs
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 1.008547ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 1.442376ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:48Z"
    - latency: 1.008559ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:48Z"
    - latency: 1.488585ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:48Z"
    - latency: 1.395596ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:48Z"
    - latency: 1.019526ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:48Z"
    - latency: 968.055µs
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:48Z"
    - latency: 1.917559ms
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:48Z"
    - latency: 935.621µs
      message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-network-check-target-ip-10-0-136-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "150001"
    uid: b5d46151-754c-416e-b593-2f1c612a2c0d
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:48Z"
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204467ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 2.520727ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 2.359205ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:48Z"
    - latency: 2.348539ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:48Z"
    - latency: 2.346465ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:48Z"
    - latency: 2.548464ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:48Z"
    - latency: 2.338209ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:48Z"
    - latency: 2.094959ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:48Z"
    - latency: 2.76128ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:48Z"
    - latency: 2.206112ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-network-check-target-ip-10-0-138-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "150002"
    uid: 2f4a8e21-3a78-4e49-9933-b086dce64265
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:48Z"
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.806089ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 2.504535ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 2.723048ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:48Z"
    - latency: 2.313014ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:48Z"
    - latency: 3.011621ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:48Z"
    - latency: 2.59221ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:48Z"
    - latency: 2.435383ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:48Z"
    - latency: 2.268455ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:48Z"
    - latency: 2.207893ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:48Z"
    - latency: 2.120108ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-173-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-173.ec2.internal
      uid: 10ee7fdd-a1b4-4dfb-a7a1-3fab395006d4
    resourceVersion: "153274"
    uid: 3dd4872f-d314-4acc-8efe-a3997012aa7b
  spec:
    sourcePod: network-check-source-6f78d59f99-dvtwf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:39:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.443348ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:39:48Z"
    - latency: 1.924018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:39:48Z"
    - latency: 1.612033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:38:48Z"
    - latency: 2.385698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:38:48Z"
    - latency: 1.283145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:37:48Z"
    - latency: 2.909201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:37:48Z"
    - latency: 918.926µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 1.766725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:36:48Z"
    - latency: 1.052789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:48Z"
    - latency: 1.900076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:35:48Z"
kind: List
metadata:
  resourceVersion: ""