apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "84253"
    uid: 54d91999-0231-498c-b9ee-51f50ff7beff
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:05:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.449µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:43Z"
    - latency: 1.013056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:43Z"
    - latency: 987.231µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:43Z"
    - latency: 986.026µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 5.444046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 1.277466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 1.107918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 976.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 1.133125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:43Z"
    - latency: 903.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "80602"
    uid: ea85ff0f-f38d-4132-98c2-6d08210cd0f8
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:04:43Z"
      message: 'load-balancer-api-external: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.445433ms
      message: 'load-balancer-api-external: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 10.165322ms
      message: 'load-balancer-api-external: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 4.99687ms
      message: 'load-balancer-api-external: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 27.954484ms
      message: 'load-balancer-api-external: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 5.775008ms
      message: 'load-balancer-api-external: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 9.278665ms
      message: 'load-balancer-api-external: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 5.019442ms
      message: 'load-balancer-api-external: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 8.652109ms
      message: 'load-balancer-api-external: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 4.715283ms
      message: 'load-balancer-api-external: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 8.179215ms
      message: 'load-balancer-api-external: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "80603"
    uid: f8e22316-a6d0-4a32-95fc-cae7fba571f8
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:04:43Z"
      message: 'load-balancer-api-internal: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.44882ms
      message: 'load-balancer-api-internal: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 10.146073ms
      message: 'load-balancer-api-internal: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 5.037808ms
      message: 'load-balancer-api-internal: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 27.90632ms
      message: 'load-balancer-api-internal: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 4.462667ms
      message: 'load-balancer-api-internal: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 9.249884ms
      message: 'load-balancer-api-internal: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 5.001341ms
      message: 'load-balancer-api-internal: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 8.622553ms
      message: 'load-balancer-api-internal: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 4.669762ms
      message: 'load-balancer-api-internal: tcp connection to a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 8.137464ms
      message: 'load-balancer-api-internal: resolved host name a826d637dc166492b9f9bf6a1d1b5466-2754923c06807f91.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-132-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "84252"
    uid: 825db8a0-9314-4541-a81a-9f1f0d632578
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:05:43Z"
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.478826ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:43Z"
    - latency: 2.220397ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:43Z"
    - latency: 2.239933ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:43Z"
    - latency: 2.526962ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 5.716413ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 2.631802ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 2.282215ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 2.356446ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 2.388708ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:43Z"
    - latency: 2.149639ms
      message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-135-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "84251"
    uid: 81c74c10-39f3-4436-90a9-93b802af5d15
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:05:43Z"
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.482679ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:43Z"
    - latency: 1.86424ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:43Z"
    - latency: 2.591354ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:43Z"
    - latency: 2.424068ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 7.523112ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 2.120458ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 2.374514ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 2.359201ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 1.943715ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:43Z"
    - latency: 1.867654ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-140-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "84250"
    uid: 51741785-c628-44e0-9c18-5e7ec975d9fb
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:05:43Z"
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.121µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:43Z"
    - latency: 932.491µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:43Z"
    - latency: 1.023632ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:43Z"
    - latency: 1.050075ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 4.996452ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 1.554728ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 927.226µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 935.04µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 986.893µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:43Z"
    - latency: 1.539667ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T03:58:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.ec2.internal
      uid: 0e2ee324-1e19-4b70-8a4a-5a579d53af50
    resourceVersion: "80601"
    uid: 99a2d9c2-0e6e-4ea9-a444-17e222609b5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-tfx27
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:04:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006711ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 1.79129ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:58:43Z"
    - latency: 4.471602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 5.954611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:57:43Z"
    - latency: 924.698µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 2.227987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:56:43Z"
    - latency: 803.667µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 1.678531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:55:43Z"
    - latency: 1.339555ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:43Z"
    - latency: 1.845162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T04:54:43Z"
kind: List
metadata:
  resourceVersion: ""