apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62362"
    uid: e068b452-182b-448f-8a30-3db2734099ec
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:59:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.810998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 711.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 843.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 1.004465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 1.23512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 2.017922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:29:27Z"
    - latency: 1.184303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:28:27Z"
    - latency: 1.819675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:27:27Z"
    - latency: 1.072482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:26:27Z"
    - latency: 823.546µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62364"
    uid: 5e2d26e3-2353-4190-b21e-474ad3c52182
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:58:27Z"
      message: 'load-balancer-api-external: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.566967ms
      message: 'load-balancer-api-external: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 13.986135ms
      message: 'load-balancer-api-external: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 5.239642ms
      message: 'load-balancer-api-external: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 7.116954ms
      message: 'load-balancer-api-external: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 4.16727ms
      message: 'load-balancer-api-external: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 8.939306ms
      message: 'load-balancer-api-external: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 4.067731ms
      message: 'load-balancer-api-external: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 8.070269ms
      message: 'load-balancer-api-external: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 4.867008ms
      message: 'load-balancer-api-external: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 8.921212ms
      message: 'load-balancer-api-external: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:30:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62363"
    uid: d0a5ec53-45a9-4ded-b95e-46ca539e7181
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:58:27Z"
      message: 'load-balancer-api-internal: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.565473ms
      message: 'load-balancer-api-internal: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 13.964111ms
      message: 'load-balancer-api-internal: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 4.073574ms
      message: 'load-balancer-api-internal: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 7.059994ms
      message: 'load-balancer-api-internal: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 4.160468ms
      message: 'load-balancer-api-internal: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 8.99923ms
      message: 'load-balancer-api-internal: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 4.820984ms
      message: 'load-balancer-api-internal: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 8.156577ms
      message: 'load-balancer-api-internal: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 4.370468ms
      message: 'load-balancer-api-internal: tcp connection to a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 8.884172ms
      message: 'load-balancer-api-internal: resolved host name a78cf0f78edc943db90f50eba30e1ce6-f986086b25c97221.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:30:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-network-check-target-ip-10-0-130-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62358"
    uid: 9f756fe8-f802-4120-9edf-0350b72a1b11
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:59:27Z"
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.409µs
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 1.516524ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 1.603318ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 1.074038ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 846.136µs
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 1.318083ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:29:27Z"
    - latency: 1.51418ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:28:27Z"
    - latency: 1.839379ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:27:27Z"
    - latency: 1.070576ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:26:27Z"
    - latency: 1.398423ms
      message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-network-check-target-ip-10-0-136-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62359"
    uid: 34b6a772-f7d8-41e8-b0f4-e09729208420
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:59:27Z"
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.440094ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 2.313957ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 2.339627ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 2.042559ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 2.21079ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 3.223919ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:29:27Z"
    - latency: 2.309165ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:28:27Z"
    - latency: 2.510945ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:27:27Z"
    - latency: 2.259403ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:26:27Z"
    - latency: 2.122209ms
      message: 'network-check-target-ip-10-0-136-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-network-check-target-ip-10-0-137-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62360"
    uid: 97dcea8a-a416-4076-9f96-2072d8e10840
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:59:27Z"
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.024756ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 2.007051ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 2.022151ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 1.842258ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 1.965279ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 2.063202ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:29:27Z"
    - latency: 1.940138ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:28:27Z"
    - latency: 1.872097ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:27:27Z"
    - latency: 2.067068ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:26:27Z"
    - latency: 1.854058ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T11:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-242-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-242.ec2.internal
      uid: 8b746bd7-b8cb-4b8e-a8b4-f3e026985920
    resourceVersion: "62361"
    uid: 8785582d-256d-43dd-a6ac-f1827645f740
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zqdxc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T11:58:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 2.39857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:34:27Z"
    - latency: 851.01µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 2.086995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:33:27Z"
    - latency: 888.662µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 2.216818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:32:27Z"
    - latency: 1.385183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 1.679949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:31:27Z"
    - latency: 1.194248ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T12:30:27Z"
    - latency: 1.848595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T12:30:27Z"
kind: List
metadata:
  resourceVersion: ""