apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "69468"
    uid: 8b72e792-459f-40ca-a2fd-47b246234dc3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.418762ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:34:11Z"
    - latency: 1.075474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 1.281533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 936.539µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 1.111991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 791.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 1.843165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:28:11Z"
    - latency: 1.540299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:27:11Z"
    - latency: 1.631811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:26:11Z"
    - latency: 1.210997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "68523"
    uid: 8ef15823-7633-4cc5-894d-16ed391dfb18
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:51:11Z"
      message: 'load-balancer-api-external: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.919908ms
      message: 'load-balancer-api-external: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 6.55435ms
      message: 'load-balancer-api-external: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 6.123296ms
      message: 'load-balancer-api-external: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 9.368905ms
      message: 'load-balancer-api-external: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 4.266711ms
      message: 'load-balancer-api-external: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 6.390392ms
      message: 'load-balancer-api-external: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 3.798502ms
      message: 'load-balancer-api-external: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 13.670706ms
      message: 'load-balancer-api-external: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 5.638511ms
      message: 'load-balancer-api-external: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 6.570874ms
      message: 'load-balancer-api-external: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:29:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "68522"
    uid: 521e7dca-10e0-43a4-a936-bb15f0501c70
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:51:11Z"
      message: 'load-balancer-api-internal: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.908883ms
      message: 'load-balancer-api-internal: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 6.664581ms
      message: 'load-balancer-api-internal: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 6.058468ms
      message: 'load-balancer-api-internal: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 9.316996ms
      message: 'load-balancer-api-internal: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 4.327162ms
      message: 'load-balancer-api-internal: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 6.265739ms
      message: 'load-balancer-api-internal: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 5.860414ms
      message: 'load-balancer-api-internal: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 13.585339ms
      message: 'load-balancer-api-internal: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 5.655722ms
      message: 'load-balancer-api-internal: tcp connection to a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 6.532338ms
      message: 'load-balancer-api-internal: resolved host name a7812dcaa0c344752bd27d0ec3634610-3e8d25b00ca74c6c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:29:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-network-check-target-ip-10-0-130-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "69465"
    uid: 4c3bc627-020d-43a3-b5b6-6b3ad6a0fdbe
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:11Z"
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.237201ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:34:11Z"
    - latency: 2.396279ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 2.547683ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 2.283536ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 2.539461ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 2.224968ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 2.209811ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:28:11Z"
    - latency: 2.468119ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:27:11Z"
    - latency: 2.35845ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:26:11Z"
    - latency: 2.56952ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-network-check-target-ip-10-0-134-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "69466"
    uid: fc72add7-1a70-4975-8d3f-4781677c92c9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:11Z"
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.435579ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:34:11Z"
    - latency: 2.344786ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 2.331999ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 2.385583ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 2.760956ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 2.006987ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 2.551939ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:28:11Z"
    - latency: 2.582193ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:27:11Z"
    - latency: 2.334042ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:26:11Z"
    - latency: 2.320448ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-network-check-target-ip-10-0-135-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "69464"
    uid: 03246a10-1168-4833-8ec9-adf007fb310e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:11Z"
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.103134ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:34:11Z"
    - latency: 1.147426ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 1.001158ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 959.171µs
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 990.733µs
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 1.076904ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 983.451µs
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:28:11Z"
    - latency: 1.193713ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:27:11Z"
    - latency: 1.643748ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:26:11Z"
    - latency: 1.585155ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:45:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-55.ec2.internal
      uid: 787b02c4-6c6e-4522-acc4-4d77b1d9df75
    resourceVersion: "68520"
    uid: 8ef8d27e-605f-4624-8231-41880fd3b8be
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgwgw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:51:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033633ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 1.918243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:33:11Z"
    - latency: 930.04µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 1.968144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:32:11Z"
    - latency: 874.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 1.701906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:31:11Z"
    - latency: 1.034977ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 2.47673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:30:11Z"
    - latency: 849.616µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:29:11Z"
    - latency: 2.309333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:29:11Z"
kind: List
metadata:
  resourceVersion: ""