apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "43865"
    uid: 4e0b0454-ff84-4a89-af6e-c5a184ed2927
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:32:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 1.253447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 1.213393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 2.519438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:50:35Z"
    - latency: 1.401842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:49:35Z"
    - latency: 1.059314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:48:35Z"
    - latency: 1.008879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:47:35Z"
    - latency: 1.279994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:46:35Z"
    - latency: 1.365616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:45:35Z"
    - latency: 931.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:44:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "46002"
    uid: 0dec2dde-d57f-4d6c-8b09-8ee7b98394c0
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:31:35Z"
      message: 'load-balancer-api-external: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.660147ms
      message: 'load-balancer-api-external: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:55:35Z"
    - latency: 7.306039ms
      message: 'load-balancer-api-external: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:55:35Z"
    - latency: 3.417365ms
      message: 'load-balancer-api-external: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:54:35Z"
    - latency: 8.277882ms
      message: 'load-balancer-api-external: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:54:35Z"
    - latency: 4.997695ms
      message: 'load-balancer-api-external: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 7.854619ms
      message: 'load-balancer-api-external: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 3.614353ms
      message: 'load-balancer-api-external: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 7.473728ms
      message: 'load-balancer-api-external: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 4.035037ms
      message: 'load-balancer-api-external: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 6.321752ms
      message: 'load-balancer-api-external: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:51:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "46001"
    uid: 7a7cf5c4-91f5-4a82-abc2-87a6f656806b
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:31:35Z"
      message: 'load-balancer-api-internal: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.683176ms
      message: 'load-balancer-api-internal: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:55:35Z"
    - latency: 7.362717ms
      message: 'load-balancer-api-internal: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:55:35Z"
    - latency: 3.45926ms
      message: 'load-balancer-api-internal: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:54:35Z"
    - latency: 8.253033ms
      message: 'load-balancer-api-internal: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:54:35Z"
    - latency: 4.024666ms
      message: 'load-balancer-api-internal: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 7.871315ms
      message: 'load-balancer-api-internal: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 3.669357ms
      message: 'load-balancer-api-internal: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 7.463961ms
      message: 'load-balancer-api-internal: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 3.535291ms
      message: 'load-balancer-api-internal: tcp connection to a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 6.311997ms
      message: 'load-balancer-api-internal: resolved host name a047148ca83e142ef8ba1b7a558a4f13-ce81420a045d4907.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:51:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-network-check-target-ip-10-0-129-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "43862"
    uid: f50117bf-3112-4618-a861-2f6ac35bdadb
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:32:35Z"
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.625311ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 2.216441ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 2.160728ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 3.466673ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:50:35Z"
    - latency: 2.135427ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:49:35Z"
    - latency: 2.155171ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:48:35Z"
    - latency: 2.094422ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:47:35Z"
    - latency: 2.310252ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:46:35Z"
    - latency: 1.706566ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:45:35Z"
    - latency: 2.011153ms
      message: 'network-check-target-ip-10-0-129-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:44:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-network-check-target-ip-10-0-138-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "43864"
    uid: 6fc76ffb-a4da-4416-83d5-887691db0783
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:32:35Z"
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.125µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 793.626µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 928.241µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 1.11416ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:50:35Z"
    - latency: 927.267µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:49:35Z"
    - latency: 924.907µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:48:35Z"
    - latency: 913.782µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:47:35Z"
    - latency: 1.022289ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:46:35Z"
    - latency: 876.954µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:45:35Z"
    - latency: 950.73µs
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:44:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-network-check-target-ip-10-0-142-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "43863"
    uid: 91399858-0210-4998-90ad-919454ca0869
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:32:35Z"
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.231249ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 2.426822ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 2.345254ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 3.072622ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:50:35Z"
    - latency: 2.299583ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:49:35Z"
    - latency: 2.187956ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:48:35Z"
    - latency: 2.090127ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:47:35Z"
    - latency: 2.585521ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:46:35Z"
    - latency: 2.354335ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:45:35Z"
    - latency: 2.272808ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:44:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-220-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-220.ec2.internal
      uid: 1eea6d78-f162-4a7a-9cbb-3fd6548228de
    resourceVersion: "46000"
    uid: abc4571e-719b-4760-85a4-ab76857fc5a3
  spec:
    sourcePod: network-check-source-7f44b6dd87-ln6rr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T20:31:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.516µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:55:35Z"
    - latency: 1.591618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:55:35Z"
    - latency: 1.084377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:54:35Z"
    - latency: 1.831093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:54:35Z"
    - latency: 801.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 1.990712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:53:35Z"
    - latency: 877.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 2.321553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:52:35Z"
    - latency: 781.287µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T20:51:35Z"
    - latency: 1.874764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T20:51:35Z"
kind: List
metadata:
  resourceVersion: ""