apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60337"
    uid: 8f37578b-1cbd-43a8-ac78-d5c9015a0c4a
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:39:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 921.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 963.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 744.466µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 818.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 1.128808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:12Z"
    - latency: 959.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:12Z"
    - latency: 1.079287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:12Z"
    - latency: 1.446184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:12Z"
    - latency: 863.286µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60338"
    uid: 071f3221-0329-4203-b971-cc40181f6912
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:38:12Z"
      message: 'load-balancer-api-external: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.447343ms
      message: 'load-balancer-api-external: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 9.166496ms
      message: 'load-balancer-api-external: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 3.501951ms
      message: 'load-balancer-api-external: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 7.693241ms
      message: 'load-balancer-api-external: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 6.153787ms
      message: 'load-balancer-api-external: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 10.779936ms
      message: 'load-balancer-api-external: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 4.953737ms
      message: 'load-balancer-api-external: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 11.348893ms
      message: 'load-balancer-api-external: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 3.793633ms
      message: 'load-balancer-api-external: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 8.326412ms
      message: 'load-balancer-api-external: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:10:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60339"
    uid: 65d83283-8026-446d-867c-7aae19ca0fd7
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:38:12Z"
      message: 'load-balancer-api-internal: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.517537ms
      message: 'load-balancer-api-internal: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 9.224994ms
      message: 'load-balancer-api-internal: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 4.893597ms
      message: 'load-balancer-api-internal: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 7.593556ms
      message: 'load-balancer-api-internal: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 5.032336ms
      message: 'load-balancer-api-internal: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 10.824496ms
      message: 'load-balancer-api-internal: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 4.998983ms
      message: 'load-balancer-api-internal: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 11.284621ms
      message: 'load-balancer-api-internal: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 3.398156ms
      message: 'load-balancer-api-internal: tcp connection to a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 8.285542ms
      message: 'load-balancer-api-internal: resolved host name a967bf2e1b27e428abc55b8a7470bd8d-62689314bedca16f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:10:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-network-check-target-ip-10-0-129-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60333"
    uid: 3ca262fe-f7f8-4807-84f2-d17188d701b9
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:39:12Z"
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.105581ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 1.199412ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 1.072918ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 855.109µs
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 1.143836ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 967.177µs
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:12Z"
    - latency: 903.143µs
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:12Z"
    - latency: 1.108173ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:12Z"
    - latency: 965.652µs
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:12Z"
    - latency: 923.133µs
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-network-check-target-ip-10-0-129-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60334"
    uid: 2b052909-ed2c-4b8b-98ce-a1cecd789ab0
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:39:12Z"
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.630886ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 1.736208ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 1.848544ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 1.43886ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 1.77203ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 1.678166ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:12Z"
    - latency: 1.733979ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:12Z"
    - latency: 2.017804ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:12Z"
    - latency: 1.677617ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:12Z"
    - latency: 1.74996ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-network-check-target-ip-10-0-141-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60335"
    uid: c7a15932-dc88-49a4-aaa2-bceee9750bf9
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:39:12Z"
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.381585ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 2.53009ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 1.835576ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 2.035164ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 2.373964ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 2.641412ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:09:12Z"
    - latency: 2.340457ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:08:12Z"
    - latency: 2.508642ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:07:12Z"
    - latency: 2.306805ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:06:12Z"
    - latency: 2.330845ms
      message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-45.ec2.internal
      uid: e6b2fa4d-1db5-49e3-a3a3-79c27d6fafe3
    resourceVersion: "60336"
    uid: efe67d7e-d86a-4f4f-848f-5e736f63d23a
  spec:
    sourcePod: network-check-source-869dcfcdcd-d8klx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:38:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 1.678865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:14:12Z"
    - latency: 855.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 1.715473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:13:12Z"
    - latency: 864.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 1.756683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:12:12Z"
    - latency: 1.145801ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 1.683285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:11:12Z"
    - latency: 1.118341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:10:12Z"
    - latency: 2.098884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:10:12Z"
kind: List
metadata:
  resourceVersion: ""