apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "39501"
    uid: 8970884a-2ed0-42b4-bc86-10e20bec4243
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.033µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:19:45Z"
    - latency: 708.681µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 766.633µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 1.326581ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 1.042968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 1.233014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 974.058µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:13:45Z"
    - latency: 863.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:12:45Z"
    - latency: 1.108332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:11:45Z"
    - latency: 929.174µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "38988"
    uid: 9514882d-c291-4d43-9ec6-cff46f27d1c5
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:36:45Z"
      message: 'load-balancer-api-external: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.878804ms
      message: 'load-balancer-api-external: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 7.239667ms
      message: 'load-balancer-api-external: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 4.445999ms
      message: 'load-balancer-api-external: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 8.162115ms
      message: 'load-balancer-api-external: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 4.435076ms
      message: 'load-balancer-api-external: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 6.022786ms
      message: 'load-balancer-api-external: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 4.737998ms
      message: 'load-balancer-api-external: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 8.895743ms
      message: 'load-balancer-api-external: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 5.518105ms
      message: 'load-balancer-api-external: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 8.355697ms
      message: 'load-balancer-api-external: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:14:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "38987"
    uid: 2dcd30ef-2061-4643-9cf9-c714822cce9f
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:36:45Z"
      message: 'load-balancer-api-internal: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.780195ms
      message: 'load-balancer-api-internal: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 7.323485ms
      message: 'load-balancer-api-internal: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 4.442692ms
      message: 'load-balancer-api-internal: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 8.079022ms
      message: 'load-balancer-api-internal: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 4.443989ms
      message: 'load-balancer-api-internal: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 6.112632ms
      message: 'load-balancer-api-internal: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 4.810667ms
      message: 'load-balancer-api-internal: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 8.793453ms
      message: 'load-balancer-api-internal: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 5.501169ms
      message: 'load-balancer-api-internal: tcp connection to a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 8.269224ms
      message: 'load-balancer-api-internal: resolved host name a028c0dc82ae144c0ac55fba98b0f85c-daad11a92806e655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:14:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-128-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "39498"
    uid: 9191cc91-7ec9-40b6-ba36-059a65ca1abc
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:45Z"
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.178993ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:19:45Z"
    - latency: 679.794µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 724.207µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 745.814µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 856.134µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 1.325339ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 997.608µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:13:45Z"
    - latency: 1.157191ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:12:45Z"
    - latency: 850.889µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:11:45Z"
    - latency: 913.939µs
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-130-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "39500"
    uid: fd226069-6d69-4409-9bc2-056f5bb89d5a
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:45Z"
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.891139ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:19:45Z"
    - latency: 1.816797ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 2.302384ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 2.37127ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 2.607617ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 2.20808ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 3.009084ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:13:45Z"
    - latency: 2.599695ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:12:45Z"
    - latency: 3.199261ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:11:45Z"
    - latency: 2.647217ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-139-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "39499"
    uid: fb5057f7-b563-4d6a-95c7-888c7fb42d7d
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:45Z"
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.197577ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:19:45Z"
    - latency: 2.168334ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 2.290787ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 2.1326ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 2.126479ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 2.254212ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 2.184804ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:13:45Z"
    - latency: 2.197539ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:12:45Z"
    - latency: 2.208362ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:11:45Z"
    - latency: 2.170539ms
      message: 'network-check-target-ip-10-0-139-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: 0c6f60ca-6758-4415-9d90-9eb84d63a3fa
    resourceVersion: "38986"
    uid: 88dbd4c3-3b55-48e5-892b-9337d33842c2
  spec:
    sourcePod: network-check-source-6f8b768455-b7s95
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:36:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 1.534502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:18:45Z"
    - latency: 981.626µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 1.433245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:17:45Z"
    - latency: 840.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 1.5472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:16:45Z"
    - latency: 1.230037ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 1.504141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:15:45Z"
    - latency: 853.125µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:14:45Z"
    - latency: 2.003162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:14:45Z"
kind: List
metadata:
  resourceVersion: ""