apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "89530"
    uid: af4edeac-8dd5-4163-91d6-2ead888ac1e7
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:49: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.766344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:52:45Z"
    - latency: 1.081786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:51:45Z"
    - latency: 1.114044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:50:45Z"
    - latency: 1.378606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:49:45Z"
    - latency: 835.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 1.055609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 1.33475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 1.273112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 1.057831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 1.657951ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "85966"
    uid: 1182612e-1c6e-4ab2-a56b-3f1d5e78e079
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:48:45Z"
      message: 'load-balancer-api-external: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.547376ms
      message: 'load-balancer-api-external: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 8.981483ms
      message: 'load-balancer-api-external: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 4.965302ms
      message: 'load-balancer-api-external: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 8.566115ms
      message: 'load-balancer-api-external: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 4.788983ms
      message: 'load-balancer-api-external: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 7.912722ms
      message: 'load-balancer-api-external: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 5.083253ms
      message: 'load-balancer-api-external: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 9.978438ms
      message: 'load-balancer-api-external: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 4.173846ms
      message: 'load-balancer-api-external: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 11.159559ms
      message: 'load-balancer-api-external: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "85967"
    uid: efa86782-464b-40ba-8a92-1079612d363b
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:48:45Z"
      message: 'load-balancer-api-internal: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.965316ms
      message: 'load-balancer-api-internal: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 9.078337ms
      message: 'load-balancer-api-internal: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 4.958141ms
      message: 'load-balancer-api-internal: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 8.625034ms
      message: 'load-balancer-api-internal: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 4.752613ms
      message: 'load-balancer-api-internal: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 7.972236ms
      message: 'load-balancer-api-internal: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 5.047551ms
      message: 'load-balancer-api-internal: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 9.96141ms
      message: 'load-balancer-api-internal: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 4.333967ms
      message: 'load-balancer-api-internal: tcp connection to a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 11.116782ms
      message: 'load-balancer-api-internal: resolved host name a89f6f00f7d3045eb933d4204796f67e-094000ea3af9dd8a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-network-check-target-ip-10-0-128-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "89529"
    uid: 84122ef2-6113-4559-9eb8-c44651cc0ec8
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:49:45Z"
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.363613ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:52:45Z"
    - latency: 2.428506ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:51:45Z"
    - latency: 2.171546ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:50:45Z"
    - latency: 2.445409ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:49:45Z"
    - latency: 2.462347ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 2.300103ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 2.351643ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 2.368483ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 2.392783ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 2.339864ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-network-check-target-ip-10-0-133-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "89528"
    uid: 42ef0810-f5d0-4fa8-81ed-dd847a3eef28
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:49:45Z"
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.971286ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:52:45Z"
    - latency: 1.902113ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:51:45Z"
    - latency: 1.914178ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:50:45Z"
    - latency: 1.926725ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:49:45Z"
    - latency: 2.095151ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 1.962088ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 1.927694ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 1.601373ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 2.005169ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 2.026946ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-network-check-target-ip-10-0-143-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "89527"
    uid: c1df744c-88ce-4b15-a8ea-d033c2050e34
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:49:45Z"
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.934µs
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:52:45Z"
    - latency: 1.147827ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:51:45Z"
    - latency: 1.682579ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:50:45Z"
    - latency: 1.084898ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:49:45Z"
    - latency: 945.839µs
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 993.785µs
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 1.316606ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 2.420404ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 1.098061ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 1.243373ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:42:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-134.ec2.internal
      uid: 9ace1d62-a9fb-4954-a366-0897d8275072
    resourceVersion: "85965"
    uid: 67292d8c-faba-42a8-8937-ff5b2367bcbe
  spec:
    sourcePod: network-check-source-7cbc45fddc-bcgcv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:48:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.330899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 2.423997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:48:45Z"
    - latency: 1.054746ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 1.868463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:47:45Z"
    - latency: 830.366µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 2.419764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:46:45Z"
    - latency: 1.008573ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 2.556708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:45:45Z"
    - latency: 818.267µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:45Z"
    - latency: 1.895219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:44:45Z"
kind: List
metadata:
  resourceVersion: ""