apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24995"
    uid: 8cd362eb-aea1-4edf-aa6c-3f2ae5b515fc
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.228697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 1.098023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 993.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 1.245628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 1.350081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 1.102693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:52:46Z"
    - latency: 1.292336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:51:46Z"
    - latency: 1.243492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:50:46Z"
    - latency: 1.459372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:49:46Z"
    - latency: 1.125451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24997"
    uid: 0a706dc2-1ec0-433f-b29b-7388fcedd8db
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:46Z"
      message: 'load-balancer-api-external: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.474044ms
      message: 'load-balancer-api-external: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 9.851144ms
      message: 'load-balancer-api-external: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 5.896866ms
      message: 'load-balancer-api-external: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 10.400847ms
      message: 'load-balancer-api-external: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 4.90192ms
      message: 'load-balancer-api-external: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 8.999931ms
      message: 'load-balancer-api-external: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 4.445505ms
      message: 'load-balancer-api-external: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 9.103685ms
      message: 'load-balancer-api-external: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 4.198923ms
      message: 'load-balancer-api-external: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 11.376199ms
      message: 'load-balancer-api-external: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:53:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24996"
    uid: aeb0a083-ca1d-494e-9cba-1217bd87b501
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:46Z"
      message: 'load-balancer-api-internal: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.412766ms
      message: 'load-balancer-api-internal: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 9.876032ms
      message: 'load-balancer-api-internal: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 5.89786ms
      message: 'load-balancer-api-internal: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 10.306809ms
      message: 'load-balancer-api-internal: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 5.949136ms
      message: 'load-balancer-api-internal: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 9.031589ms
      message: 'load-balancer-api-internal: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 4.267016ms
      message: 'load-balancer-api-internal: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 9.123072ms
      message: 'load-balancer-api-internal: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 3.8495ms
      message: 'load-balancer-api-internal: tcp connection to a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 11.443683ms
      message: 'load-balancer-api-internal: resolved host name a98018e2a71f949fba1d8725ad31beca-8d455f520d7a9104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:53:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-network-check-target-ip-10-0-128-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24992"
    uid: 8f7473e4-6a2b-4ca0-8d88-85258e5cc94b
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.416064ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 2.354404ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 2.280191ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 1.968231ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 2.570595ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 2.080396ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:52:46Z"
    - latency: 2.166139ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:51:46Z"
    - latency: 2.020899ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:50:46Z"
    - latency: 2.133208ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:49:46Z"
    - latency: 2.832845ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-network-check-target-ip-10-0-128-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24993"
    uid: 55c13ca5-89c7-4ea9-9c2c-97544336a60c
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.065265ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 2.230771ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 2.167318ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 2.374345ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 2.342002ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 2.384482ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:52:46Z"
    - latency: 2.182298ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:51:46Z"
    - latency: 2.606852ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:50:46Z"
    - latency: 2.09337ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:49:46Z"
    - latency: 2.011805ms
      message: 'network-check-target-ip-10-0-128-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-network-check-target-ip-10-0-142-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24991"
    uid: 53aaacb8-ba87-4da6-b200-03d8a321a653
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:22:46Z"
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.342µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 800.817µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 1.249026ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 868.195µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 1.046931ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 994.156µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:52:46Z"
    - latency: 890.728µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:51:46Z"
    - latency: 924.387µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:50:46Z"
    - latency: 1.114547ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:49:46Z"
    - latency: 855.76µs
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:15:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-96.ec2.internal
      uid: 40b922a2-31ed-4ccd-a62d-91091ea1ae4b
    resourceVersion: "24994"
    uid: 5e855464-f87d-4781-bc7f-12ec34ae7799
  spec:
    sourcePod: network-check-source-7cbc45fddc-rkzvj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.007µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 2.348618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:57:46Z"
    - latency: 784.455µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 1.907132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:56:46Z"
    - latency: 1.548489ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 2.029941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:55:46Z"
    - latency: 933.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 2.080913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:54:46Z"
    - latency: 1.413754ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:53:46Z"
    - latency: 1.885199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:53:46Z"
kind: List
metadata:
  resourceVersion: ""