apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "63976"
    uid: 09cae854-91ff-4bc1-8197-cc1f239cb35b
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:03:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.130633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 1.252625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 1.095578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 1.662042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 1.094984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:27:24Z"
    - latency: 1.320074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:26:24Z"
    - latency: 1.247275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:25:24Z"
    - latency: 1.371101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:24:24Z"
    - latency: 1.19616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:23:24Z"
    - latency: 1.435328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:22:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "64615"
    uid: d060c663-3e53-43a1-a160-6cfef2bb326c
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:02:24Z"
      message: 'load-balancer-api-external: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.516155ms
      message: 'load-balancer-api-external: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:32:24Z"
    - latency: 10.767174ms
      message: 'load-balancer-api-external: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:32:24Z"
    - latency: 6.358268ms
      message: 'load-balancer-api-external: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 11.240768ms
      message: 'load-balancer-api-external: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 4.231408ms
      message: 'load-balancer-api-external: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 13.400766ms
      message: 'load-balancer-api-external: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 4.354284ms
      message: 'load-balancer-api-external: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 14.897086ms
      message: 'load-balancer-api-external: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 5.023414ms
      message: 'load-balancer-api-external: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 10.801582ms
      message: 'load-balancer-api-external: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:28:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "64614"
    uid: b4b7f5c7-7c9c-42c0-9239-2c33fe23af83
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:02:24Z"
      message: 'load-balancer-api-internal: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.521404ms
      message: 'load-balancer-api-internal: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:32:24Z"
    - latency: 10.757099ms
      message: 'load-balancer-api-internal: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:32:24Z"
    - latency: 5.94427ms
      message: 'load-balancer-api-internal: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 11.188073ms
      message: 'load-balancer-api-internal: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 4.227674ms
      message: 'load-balancer-api-internal: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 13.375161ms
      message: 'load-balancer-api-internal: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 3.779876ms
      message: 'load-balancer-api-internal: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 14.878166ms
      message: 'load-balancer-api-internal: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 5.222963ms
      message: 'load-balancer-api-internal: tcp connection to a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 10.702708ms
      message: 'load-balancer-api-internal: resolved host name a9feb7e66563947828066d1b45a03eb4-9f7808218528b18d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:28:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-129-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "63975"
    uid: e6aebddf-7b27-41c3-a283-89ca9ac51008
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:03:24Z"
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.259873ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 1.997085ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 1.959379ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 2.357667ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 2.037439ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:27:24Z"
    - latency: 2.236779ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:26:24Z"
    - latency: 2.240198ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:25:24Z"
    - latency: 2.327844ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:24:24Z"
    - latency: 2.349303ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:23:24Z"
    - latency: 2.02384ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:22:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-138-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "63974"
    uid: 1e10bbe1-85f2-4f16-b298-996356f85a1d
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:03:24Z"
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.89915ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 1.873292ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 2.050708ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 1.948207ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 2.199081ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:27:24Z"
    - latency: 1.866363ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:26:24Z"
    - latency: 1.952973ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:25:24Z"
    - latency: 1.879364ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:24:24Z"
    - latency: 1.808331ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:23:24Z"
    - latency: 1.838105ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:22:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-139-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "63973"
    uid: d6368213-6eba-4d95-b78f-8295caafd7e0
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:03:24Z"
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.129µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 906.031µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 1.15868ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 853.058µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 1.027631ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:27:24Z"
    - latency: 983.217µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:26:24Z"
    - latency: 984.353µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:25:24Z"
    - latency: 1.564801ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:24:24Z"
    - latency: 951.282µs
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:23:24Z"
    - latency: 1.122925ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:22:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T10:56:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-204.ec2.internal
      uid: cb90c426-b969-4ca2-9dd7-4996fbc8a5c5
    resourceVersion: "64613"
    uid: 999160c1-b2c6-4fe9-80b5-61e7eeab70a7
  spec:
    sourcePod: network-check-source-6f8b768455-tt7px
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:02:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 845.115µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:32:24Z"
    - latency: 1.759149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:32:24Z"
    - latency: 1.242499ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 1.902735ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:31:24Z"
    - latency: 922.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 2.266125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:30:24Z"
    - latency: 884.667µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 1.778917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:29:24Z"
    - latency: 946.674µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T11:28:24Z"
    - latency: 1.952024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T11:28:24Z"
kind: List
metadata:
  resourceVersion: ""