apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "19436"
    uid: 1477a0a2-b59c-4f85-8f5b-edd0747124d6
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:19:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 791.513µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 958.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:31:47Z"
    - latency: 913.053µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:30:47Z"
    - latency: 1.013966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:29:47Z"
    - latency: 1.741543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:28:47Z"
    - latency: 847.891µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:27:47Z"
    - latency: 1.258247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:26:47Z"
    - latency: 876.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:25:47Z"
    - latency: 797.947µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "20798"
    uid: c79336cf-265c-4324-83ed-b4a6eb9290e0
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:18:47Z"
      message: 'load-balancer-api-external: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.127424ms
      message: 'load-balancer-api-external: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:36:47Z"
    - latency: 7.966244ms
      message: 'load-balancer-api-external: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:36:47Z"
    - latency: 4.418582ms
      message: 'load-balancer-api-external: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:35:47Z"
    - latency: 7.255283ms
      message: 'load-balancer-api-external: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:35:47Z"
    - latency: 5.075687ms
      message: 'load-balancer-api-external: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:34:47Z"
    - latency: 7.603344ms
      message: 'load-balancer-api-external: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:34:47Z"
    - latency: 5.240981ms
      message: 'load-balancer-api-external: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 7.832589ms
      message: 'load-balancer-api-external: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 3.691184ms
      message: 'load-balancer-api-external: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 8.021374ms
      message: 'load-balancer-api-external: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "20797"
    uid: f1cf5059-3d45-42a4-9faf-a0df778f64e6
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:18:47Z"
      message: 'load-balancer-api-internal: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.1165ms
      message: 'load-balancer-api-internal: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:36:47Z"
    - latency: 8.017033ms
      message: 'load-balancer-api-internal: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:36:47Z"
    - latency: 3.546911ms
      message: 'load-balancer-api-internal: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:35:47Z"
    - latency: 7.387235ms
      message: 'load-balancer-api-internal: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:35:47Z"
    - latency: 4.244016ms
      message: 'load-balancer-api-internal: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:34:47Z"
    - latency: 7.510174ms
      message: 'load-balancer-api-internal: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:34:47Z"
    - latency: 4.716738ms
      message: 'load-balancer-api-internal: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 7.900664ms
      message: 'load-balancer-api-internal: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 3.724512ms
      message: 'load-balancer-api-internal: tcp connection to a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 7.973199ms
      message: 'load-balancer-api-internal: resolved host name a45c9bf5e9170497eb82531d5a5bb760-530569e3c6922d72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-network-check-target-ip-10-0-137-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "19433"
    uid: 80461264-bb29-4348-bbb1-a6102b690ef7
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:19:47Z"
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.767245ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 1.775694ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 1.632047ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:31:47Z"
    - latency: 1.764894ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:30:47Z"
    - latency: 1.810694ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:29:47Z"
    - latency: 1.934307ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:28:47Z"
    - latency: 1.779586ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:27:47Z"
    - latency: 1.796631ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:26:47Z"
    - latency: 1.71249ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:25:47Z"
    - latency: 1.810203ms
      message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-network-check-target-ip-10-0-138-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "19435"
    uid: ddf6ad7c-ec63-45d3-a773-8eb04d7ca66c
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:19:47Z"
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.922644ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 2.153307ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 2.317936ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:31:47Z"
    - latency: 2.172453ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:30:47Z"
    - latency: 2.118382ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:29:47Z"
    - latency: 2.126144ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:28:47Z"
    - latency: 2.06584ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:27:47Z"
    - latency: 2.149498ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:26:47Z"
    - latency: 1.678754ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:25:47Z"
    - latency: 2.002371ms
      message: 'network-check-target-ip-10-0-138-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-network-check-target-ip-10-0-142-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "19434"
    uid: 1c3cff96-4996-41ac-adc6-c262cd4ba244
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:19:47Z"
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.848µs
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 1.280531ms
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 1.385124ms
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:31:47Z"
    - latency: 1.095477ms
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:30:47Z"
    - latency: 752.008µs
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:29:47Z"
    - latency: 1.77481ms
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:28:47Z"
    - latency: 805.385µs
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:27:47Z"
    - latency: 882.8µs
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:26:47Z"
    - latency: 757.429µs
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:25:47Z"
    - latency: 768.236µs
      message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:12:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-90.ec2.internal
      uid: 57beadc7-868e-449d-9106-026b53bbda81
    resourceVersion: "20796"
    uid: 9386a136-3141-4336-97d5-3ab430f2a36a
  spec:
    sourcePod: network-check-source-6f8b768455-t7hp8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:18:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:36:47Z"
    - latency: 1.687335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:36:47Z"
    - latency: 923.206µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:35:47Z"
    - latency: 1.624814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:35:47Z"
    - latency: 1.032063ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:34:47Z"
    - latency: 1.762892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:34:47Z"
    - latency: 1.254535ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 1.573501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:33:47Z"
    - latency: 809.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:32:47Z"
    - latency: 1.586298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:32:47Z"
kind: List
metadata:
  resourceVersion: ""