apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "199539"
    uid: 437efd53-dea9-4009-9914-2adc171e51f0
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:12:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.490972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:36:44Z"
    - latency: 999.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:35:44Z"
    - latency: 878.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:34:44Z"
    - latency: 1.500174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:33:44Z"
    - latency: 1.44698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:32:44Z"
    - latency: 1.542767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:31:44Z"
    - latency: 1.084451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:30:44Z"
    - latency: 1.088927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:29:44Z"
    - latency: 980.618µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:28:44Z"
    - latency: 1.379688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:27:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "203512"
    uid: bac5e2c5-e367-4509-9da0-83872b7d54fb
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:11:44Z"
      message: 'load-balancer-api-external: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 22.929293ms
      message: 'load-balancer-api-external: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:41:44Z"
    - latency: 7.734447ms
      message: 'load-balancer-api-external: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:41:44Z"
    - latency: 18.200548ms
      message: 'load-balancer-api-external: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:40:44Z"
    - latency: 7.02753ms
      message: 'load-balancer-api-external: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:40:44Z"
    - latency: 17.620284ms
      message: 'load-balancer-api-external: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:39:44Z"
    - latency: 6.812246ms
      message: 'load-balancer-api-external: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:39:44Z"
    - latency: 18.76391ms
      message: 'load-balancer-api-external: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:38:44Z"
    - latency: 7.639149ms
      message: 'load-balancer-api-external: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:38:44Z"
    - latency: 18.473268ms
      message: 'load-balancer-api-external: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:37:44Z"
    - latency: 8.186492ms
      message: 'load-balancer-api-external: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:37:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "203511"
    uid: 23932a2f-88b3-472b-824b-2488da5adbbc
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:11:44Z"
      message: 'load-balancer-api-internal: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.590263ms
      message: 'load-balancer-api-internal: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:41:44Z"
    - latency: 7.657862ms
      message: 'load-balancer-api-internal: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:41:44Z"
    - latency: 18.249474ms
      message: 'load-balancer-api-internal: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:40:44Z"
    - latency: 7.054518ms
      message: 'load-balancer-api-internal: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:40:44Z"
    - latency: 17.360667ms
      message: 'load-balancer-api-internal: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:39:44Z"
    - latency: 6.897108ms
      message: 'load-balancer-api-internal: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:39:44Z"
    - latency: 18.779203ms
      message: 'load-balancer-api-internal: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:38:44Z"
    - latency: 7.67097ms
      message: 'load-balancer-api-internal: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:38:44Z"
    - latency: 18.482586ms
      message: 'load-balancer-api-internal: tcp connection to acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:37:44Z"
    - latency: 7.990802ms
      message: 'load-balancer-api-internal: resolved host name acdab800ed9844bf4a1328dae3478168-8ed98711b3f0afe6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:37:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-130-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "199536"
    uid: 074c11ee-11c7-46af-aa76-1b74227cc6c6
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:12:44Z"
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.789358ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:36:44Z"
    - latency: 1.169618ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:35:44Z"
    - latency: 1.692027ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:34:44Z"
    - latency: 1.113452ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:33:44Z"
    - latency: 1.214351ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:32:44Z"
    - latency: 979.978µs
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:31:44Z"
    - latency: 1.367591ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:30:44Z"
    - latency: 1.486702ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:29:44Z"
    - latency: 1.095925ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:28:44Z"
    - latency: 1.148707ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:27:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-134-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "199538"
    uid: 0c3bacb3-c6d0-4d63-9e1c-2dc5b70a25cb
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:12:44Z"
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.79ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:36:44Z"
    - latency: 2.308835ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:35:44Z"
    - latency: 2.484587ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:34:44Z"
    - latency: 3.114249ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:33:44Z"
    - latency: 2.606148ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:32:44Z"
    - latency: 3.097506ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:31:44Z"
    - latency: 2.383975ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:30:44Z"
    - latency: 2.793554ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:29:44Z"
    - latency: 2.274798ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:28:44Z"
    - latency: 2.510223ms
      message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:27:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-140-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "199537"
    uid: e50f458e-a6a7-43f6-85cd-ea610ec859b5
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:12:44Z"
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.41915ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:36:44Z"
    - latency: 2.111537ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:35:44Z"
    - latency: 2.150632ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:34:44Z"
    - latency: 1.971618ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:33:44Z"
    - latency: 2.568586ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:32:44Z"
    - latency: 2.142328ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:31:44Z"
    - latency: 2.020206ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:30:44Z"
    - latency: 2.351979ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:29:44Z"
    - latency: 2.035573ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:28:44Z"
    - latency: 2.237663ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:27:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T04:05:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 23ba8b58-628b-4edf-946f-e0c4cf50bdf7
    resourceVersion: "203509"
    uid: db653b7f-055d-447b-9079-d6c4029536c6
  spec:
    sourcePod: network-check-source-6f78d59f99-rf8vj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T04:11:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.071µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:41:44Z"
    - latency: 2.216475ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:41:44Z"
    - latency: 1.184644ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:40:44Z"
    - latency: 1.821378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:40:44Z"
    - latency: 859.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:39:44Z"
    - latency: 2.119518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:39:44Z"
    - latency: 1.069015ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:38:44Z"
    - latency: 2.440118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:38:44Z"
    - latency: 901.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T05:37:44Z"
    - latency: 2.681361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T05:37:44Z"
kind: List
metadata:
  resourceVersion: ""