apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65334"
    uid: d8c39658-3cff-4f05-ba5e-f5c493b4b058
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:55:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.346005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 922.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 916.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 1.055223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 988.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 1.039687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:07:45Z"
    - latency: 1.11893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:06:45Z"
    - latency: 875.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:05:45Z"
    - latency: 1.219087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:04:45Z"
    - latency: 1.240263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65337"
    uid: 10160590-153f-499e-ac17-ba8d33cc00a3
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:54:45Z"
      message: 'load-balancer-api-external: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.886375ms
      message: 'load-balancer-api-external: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 9.420481ms
      message: 'load-balancer-api-external: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 5.480968ms
      message: 'load-balancer-api-external: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 9.496767ms
      message: 'load-balancer-api-external: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 5.150378ms
      message: 'load-balancer-api-external: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 8.541863ms
      message: 'load-balancer-api-external: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 5.186551ms
      message: 'load-balancer-api-external: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 8.343062ms
      message: 'load-balancer-api-external: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 6.369296ms
      message: 'load-balancer-api-external: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 8.911718ms
      message: 'load-balancer-api-external: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:08:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65336"
    uid: d7277e63-5a24-4ed6-a1c8-b52b598dcad9
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:54:45Z"
      message: 'load-balancer-api-internal: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.300225ms
      message: 'load-balancer-api-internal: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 9.351789ms
      message: 'load-balancer-api-internal: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 5.503822ms
      message: 'load-balancer-api-internal: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 10.572656ms
      message: 'load-balancer-api-internal: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 4.417214ms
      message: 'load-balancer-api-internal: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 8.611032ms
      message: 'load-balancer-api-internal: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 5.210428ms
      message: 'load-balancer-api-internal: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 8.26378ms
      message: 'load-balancer-api-internal: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 6.412354ms
      message: 'load-balancer-api-internal: tcp connection to a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 8.862788ms
      message: 'load-balancer-api-internal: resolved host name a692ccb1eeed14afa90aadf4cc55a129-e6f7d1a45d273665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:08:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-network-check-target-ip-10-0-137-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65330"
    uid: 650d3f94-9f84-4401-9555-6fa1d9a71642
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:55:45Z"
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264006ms
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 1.092038ms
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 1.070849ms
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 1.314277ms
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 1.532639ms
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 2.016238ms
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:07:45Z"
    - latency: 938.089µs
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:06:45Z"
    - latency: 940.561µs
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:05:45Z"
    - latency: 714.704µs
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:04:45Z"
    - latency: 656.062µs
      message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-network-check-target-ip-10-0-138-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65333"
    uid: 1e50901a-9e9e-4a56-854f-aabea5dd1e5d
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:55:45Z"
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.471827ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 2.393389ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 2.147748ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 2.051598ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 2.244801ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 2.593837ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:07:45Z"
    - latency: 2.267695ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:06:45Z"
    - latency: 2.029831ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:05:45Z"
    - latency: 2.170527ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:04:45Z"
    - latency: 2.44516ms
      message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-network-check-target-ip-10-0-143-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65331"
    uid: 0dcc4e53-e9fc-4854-9a1b-eb4ca9d6c518
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:55:45Z"
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.76929ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 1.759924ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 1.499711ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 1.705832ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 1.855275ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 2.074987ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:07:45Z"
    - latency: 1.874926ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:06:45Z"
    - latency: 1.785982ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:05:45Z"
    - latency: 1.786275ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:04:45Z"
    - latency: 1.549259ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-68-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-68.ec2.internal
      uid: 35f60ca8-53a0-4ded-b8ac-3f51aba8cf85
    resourceVersion: "65332"
    uid: 79a11a1c-6418-4bd5-8985-395f88f3cf11
  spec:
    sourcePod: network-check-source-8894fc9bd-rltbp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T17:54:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.426µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 2.647339ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:12:45Z"
    - latency: 1.093451ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 1.74532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:11:45Z"
    - latency: 766.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 3.264718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:10:45Z"
    - latency: 845.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 1.663428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:09:45Z"
    - latency: 848.01µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:08:45Z"
    - latency: 2.049158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:08:45Z"
kind: List
metadata:
  resourceVersion: ""