apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "22214"
    uid: 1f885ef0-06c1-46d7-a868-c8868c47aa12
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:27:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.151713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:48:54Z"
    - latency: 873.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:47:54Z"
    - latency: 1.360983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:46:54Z"
    - latency: 938.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:45:54Z"
    - latency: 916.589µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 873.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 1.499208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 1.056655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 831.293µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 1.168506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:39:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "20501"
    uid: 3e26bc74-7403-491e-acd9-af05db36f00e
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:26:54Z"
      message: 'load-balancer-api-external: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.873944ms
      message: 'load-balancer-api-external: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 7.909107ms
      message: 'load-balancer-api-external: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 6.815438ms
      message: 'load-balancer-api-external: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 9.149869ms
      message: 'load-balancer-api-external: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 5.019295ms
      message: 'load-balancer-api-external: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 13.90735ms
      message: 'load-balancer-api-external: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 3.542357ms
      message: 'load-balancer-api-external: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 8.297176ms
      message: 'load-balancer-api-external: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 3.353951ms
      message: 'load-balancer-api-external: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 9.330745ms
      message: 'load-balancer-api-external: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:40:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "20502"
    uid: b8b59bd7-ee5e-4de9-a7e5-94d372868ba4
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:26:54Z"
      message: 'load-balancer-api-internal: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.936746ms
      message: 'load-balancer-api-internal: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 8.025878ms
      message: 'load-balancer-api-internal: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 6.794773ms
      message: 'load-balancer-api-internal: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 9.068212ms
      message: 'load-balancer-api-internal: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 4.778503ms
      message: 'load-balancer-api-internal: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 14.112331ms
      message: 'load-balancer-api-internal: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 5.32374ms
      message: 'load-balancer-api-internal: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 8.22676ms
      message: 'load-balancer-api-internal: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 4.212773ms
      message: 'load-balancer-api-internal: tcp connection to a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 9.396313ms
      message: 'load-balancer-api-internal: resolved host name a9eb95f534c01429ab70a432bc5f7291-9470c9b2ab032f16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:40:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-network-check-target-ip-10-0-128-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "22213"
    uid: 1e0600c9-989a-4daa-94f9-97b9898b5c03
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:27:54Z"
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.322011ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:48:54Z"
    - latency: 2.168707ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:47:54Z"
    - latency: 2.408322ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:46:54Z"
    - latency: 2.227969ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:45:54Z"
    - latency: 2.168757ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 2.058224ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 2.371892ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 2.055887ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 2.207829ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 2.166039ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:39:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-network-check-target-ip-10-0-132-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "22212"
    uid: 9de0ea72-156f-4336-ad92-0b8a59f4d19c
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:27:54Z"
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16432ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:48:54Z"
    - latency: 1.80424ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:47:54Z"
    - latency: 2.252444ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:46:54Z"
    - latency: 1.594123ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:45:54Z"
    - latency: 1.879127ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 2.11354ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 1.781133ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 1.731928ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 1.850237ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 1.872123ms
      message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:39:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-network-check-target-ip-10-0-134-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "22211"
    uid: c2e2ff6a-3f3e-4c72-8590-37b35b3ab328
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:27:54Z"
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.138µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:48:54Z"
    - latency: 920.117µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:47:54Z"
    - latency: 963.752µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:46:54Z"
    - latency: 838.17µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:45:54Z"
    - latency: 901.38µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 848.002µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 1.922815ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 856.038µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 878.49µs
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 1.410927ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:39:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:20:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-85.ec2.internal
      uid: dae55817-647d-4f25-82d3-dbc16dbfc1b6
    resourceVersion: "20500"
    uid: cdd30121-baba-4491-b41c-d8af4e8eea45
  spec:
    sourcePod: network-check-source-685456655f-hb4kc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:26:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148323ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 1.678112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:44:54Z"
    - latency: 853.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 2.587769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:43:54Z"
    - latency: 1.029352ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 1.94252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:42:54Z"
    - latency: 774.998µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 1.657227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:41:54Z"
    - latency: 781.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:40:54Z"
    - latency: 1.975163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:40:54Z"
kind: List
metadata:
  resourceVersion: ""