apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56767"
    uid: b72f910a-5592-44b6-af9e-7dffadea4ab3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:32:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.441228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 1.176305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 947.135µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 969.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 1.226375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 874.669µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:02:48Z"
    - latency: 1.73299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:01:48Z"
    - latency: 1.19956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:00:48Z"
    - latency: 1.175753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:59:48Z"
    - latency: 1.272205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:58:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56769"
    uid: 013f63fb-2f5f-449c-93c2-67b01ac3683e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:31:48Z"
      message: 'load-balancer-api-external: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.615755ms
      message: 'load-balancer-api-external: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 8.188236ms
      message: 'load-balancer-api-external: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 4.603814ms
      message: 'load-balancer-api-external: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 8.526045ms
      message: 'load-balancer-api-external: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 4.282846ms
      message: 'load-balancer-api-external: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 7.001764ms
      message: 'load-balancer-api-external: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 4.324732ms
      message: 'load-balancer-api-external: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 6.732547ms
      message: 'load-balancer-api-external: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 4.246107ms
      message: 'load-balancer-api-external: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 6.427785ms
      message: 'load-balancer-api-external: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56768"
    uid: 1d406097-b4ca-4316-8872-9cc15b1b0eac
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:31:48Z"
      message: 'load-balancer-api-internal: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.556828ms
      message: 'load-balancer-api-internal: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 8.207908ms
      message: 'load-balancer-api-internal: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 5.502453ms
      message: 'load-balancer-api-internal: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 8.453956ms
      message: 'load-balancer-api-internal: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 3.721899ms
      message: 'load-balancer-api-internal: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 6.972097ms
      message: 'load-balancer-api-internal: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 3.553423ms
      message: 'load-balancer-api-internal: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 6.764335ms
      message: 'load-balancer-api-internal: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 4.190775ms
      message: 'load-balancer-api-internal: tcp connection to ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 6.367486ms
      message: 'load-balancer-api-internal: resolved host name ab8b56e83c0684c21922a34ac04b63b1-da1461369509dfbd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-network-check-target-ip-10-0-128-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56765"
    uid: e2fefb83-b4f7-4d9a-9a94-b482e11cd02f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:32:48Z"
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.386559ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 2.539373ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 2.284363ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 2.25974ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 2.641098ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 2.261601ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:02:48Z"
    - latency: 2.709491ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:01:48Z"
    - latency: 2.37362ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:00:48Z"
    - latency: 2.375841ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:59:48Z"
    - latency: 2.280744ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:58:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-network-check-target-ip-10-0-133-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56764"
    uid: 58c9c3a3-b86a-47d9-9d99-d9dc2ca234fd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:32:48Z"
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.26107ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 1.30448ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 765.332µs
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 912.106µs
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 948.313µs
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 880.436µs
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:02:48Z"
    - latency: 1.230351ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:01:48Z"
    - latency: 939.051µs
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:00:48Z"
    - latency: 1.277063ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:59:48Z"
    - latency: 855.352µs
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:58:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-network-check-target-ip-10-0-136-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56766"
    uid: c260e000-7bf7-4a60-a76b-d9fa1edb4475
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:32:48Z"
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.867443ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 1.90011ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 1.857352ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 1.99391ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 2.029531ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 1.894408ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:02:48Z"
    - latency: 2.226505ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:01:48Z"
    - latency: 2.314726ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:00:48Z"
    - latency: 2.038138ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:59:48Z"
    - latency: 2.130224ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T22:58:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:25:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-100.ec2.internal
      uid: 664383b8-09d1-475a-b9fe-7e418f31e9a4
    resourceVersion: "56763"
    uid: 65ce9e3c-f229-45c4-9b31-d915a40bf525
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w24zn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T22:31:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 1.886355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:07:48Z"
    - latency: 907.181µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 1.833671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:06:48Z"
    - latency: 876.916µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 1.690289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:05:48Z"
    - latency: 1.174677ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 2.077779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:04:48Z"
    - latency: 1.546855ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:03:48Z"
    - latency: 1.697883ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:03:48Z"
kind: List
metadata:
  resourceVersion: ""