apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63275"
    uid: c962e2e5-aa36-4bda-9b42-81d43d96a382
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:21:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.083561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 1.572472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 1.170356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 1.067426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 910.673µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 924.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:51:09Z"
    - latency: 1.000849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:50:09Z"
    - latency: 1.607519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:49:09Z"
    - latency: 1.147071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:48:09Z"
    - latency: 1.37864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63278"
    uid: e63e4427-0fc2-49ad-90d9-213a5d338fce
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:20:09Z"
      message: 'load-balancer-api-external: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.213919ms
      message: 'load-balancer-api-external: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 9.119667ms
      message: 'load-balancer-api-external: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 3.90488ms
      message: 'load-balancer-api-external: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 8.706209ms
      message: 'load-balancer-api-external: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 4.731396ms
      message: 'load-balancer-api-external: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 8.281454ms
      message: 'load-balancer-api-external: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 3.824936ms
      message: 'load-balancer-api-external: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 8.139195ms
      message: 'load-balancer-api-external: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 5.046454ms
      message: 'load-balancer-api-external: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 8.600239ms
      message: 'load-balancer-api-external: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:52:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63277"
    uid: 6b3fcefb-a272-48eb-9eaa-41c74ca65f73
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:20:09Z"
      message: 'load-balancer-api-internal: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.24034ms
      message: 'load-balancer-api-internal: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 9.092376ms
      message: 'load-balancer-api-internal: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 3.912596ms
      message: 'load-balancer-api-internal: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 8.666844ms
      message: 'load-balancer-api-internal: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 4.698977ms
      message: 'load-balancer-api-internal: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 8.304868ms
      message: 'load-balancer-api-internal: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 3.703855ms
      message: 'load-balancer-api-internal: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 8.111546ms
      message: 'load-balancer-api-internal: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 4.991772ms
      message: 'load-balancer-api-internal: tcp connection to a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 8.587451ms
      message: 'load-balancer-api-internal: resolved host name a643fe31d63694f34a7d0c5f3ab74f9c-08d3862028dc4567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:52:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-network-check-target-ip-10-0-138-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63273"
    uid: 491da019-1a90-4ba9-bc39-d7e8d542566a
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:21:09Z"
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.059657ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 2.499643ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 2.273921ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 2.111627ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 2.222692ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 2.342581ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:51:09Z"
    - latency: 2.372464ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:50:09Z"
    - latency: 2.239204ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:49:09Z"
    - latency: 2.525086ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:48:09Z"
    - latency: 2.567696ms
      message: 'network-check-target-ip-10-0-138-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-network-check-target-ip-10-0-139-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63271"
    uid: 24147a59-9414-4e89-96f4-2d6bfe9615c5
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:21:09Z"
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.391µs
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 1.776954ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 934.655µs
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 1.489736ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 1.283011ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 1.144812ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:51:09Z"
    - latency: 1.021636ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:50:09Z"
    - latency: 881.77µs
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:49:09Z"
    - latency: 1.029252ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:48:09Z"
    - latency: 1.419747ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-network-check-target-ip-10-0-143-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63272"
    uid: 062e32c5-ca3d-41d8-acac-837a6e4797e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:21:09Z"
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.785406ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 2.000313ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 1.691688ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 2.036267ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 1.872323ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 1.984116ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:51:09Z"
    - latency: 2.015193ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:50:09Z"
    - latency: 2.169634ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:49:09Z"
    - latency: 2.141282ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:48:09Z"
    - latency: 2.031023ms
      message: 'network-check-target-ip-10-0-143-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-11T01:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-236-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-236.ec2.internal
      uid: 758d790d-a873-4388-86aa-293aa41d0883
    resourceVersion: "63274"
    uid: 2721bcc7-7bac-4824-97ad-a73abd89201d
  spec:
    sourcePod: network-check-source-869dcfcdcd-g55bb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-11T01:20:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.234µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 1.88035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:56:09Z"
    - latency: 874.545µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 2.261822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:55:09Z"
    - latency: 1.447103ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 1.838108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:54:09Z"
    - latency: 1.083055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 1.713251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:53:09Z"
    - latency: 1.086783ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-11T01:52:09Z"
    - latency: 1.934533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-11T01:52:09Z"
kind: List
metadata:
  resourceVersion: ""