apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "69305"
    uid: 93af01a9-4758-4b21-a52e-d387fcd1fcc7
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.742µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 888.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 1.329651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 1.145549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 1.37201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:49:51Z"
    - latency: 1.000325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:48:51Z"
    - latency: 1.227082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:47:51Z"
    - latency: 1.383324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:46:51Z"
    - latency: 1.679014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:51Z"
    - latency: 946.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "70331"
    uid: 2124b575-3448-490b-b311-6153cce5e694
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:24:51Z"
      message: 'load-balancer-api-external: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.625474ms
      message: 'load-balancer-api-external: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:54:51Z"
    - latency: 7.513489ms
      message: 'load-balancer-api-external: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:54:51Z"
    - latency: 5.453093ms
      message: 'load-balancer-api-external: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 6.13714ms
      message: 'load-balancer-api-external: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 3.796006ms
      message: 'load-balancer-api-external: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 8.948739ms
      message: 'load-balancer-api-external: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 3.434625ms
      message: 'load-balancer-api-external: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 8.061279ms
      message: 'load-balancer-api-external: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 5.089804ms
      message: 'load-balancer-api-external: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 12.833911ms
      message: 'load-balancer-api-external: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:50:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "70332"
    uid: b5c5424a-4cb1-450f-a74a-520fc8ec8ba4
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:24:51Z"
      message: 'load-balancer-api-internal: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.693836ms
      message: 'load-balancer-api-internal: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:54:51Z"
    - latency: 7.457474ms
      message: 'load-balancer-api-internal: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:54:51Z"
    - latency: 5.458288ms
      message: 'load-balancer-api-internal: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 6.187315ms
      message: 'load-balancer-api-internal: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 4.53761ms
      message: 'load-balancer-api-internal: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 8.884651ms
      message: 'load-balancer-api-internal: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 3.442718ms
      message: 'load-balancer-api-internal: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 7.979628ms
      message: 'load-balancer-api-internal: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 5.081594ms
      message: 'load-balancer-api-internal: tcp connection to aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 12.733995ms
      message: 'load-balancer-api-internal: resolved host name aa0a64b4d367d4c8799845b81e6594f6-56833b151b25644f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:50:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-network-check-target-ip-10-0-136-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "69302"
    uid: f44f20e6-a90e-4a21-941f-97dc47687baa
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:51Z"
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.159µs
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 926.675µs
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 1.13485ms
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 934.282µs
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 1.070895ms
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:49:51Z"
    - latency: 1.212727ms
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:48:51Z"
    - latency: 1.052274ms
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:47:51Z"
    - latency: 1.077559ms
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:46:51Z"
    - latency: 1.236654ms
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:51Z"
    - latency: 976.679µs
      message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-network-check-target-ip-10-0-140-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "69303"
    uid: b812af55-0c35-459d-bfc6-104258d0e4fe
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:51Z"
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.336928ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 2.176341ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 2.26804ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 2.443603ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 2.098029ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:49:51Z"
    - latency: 1.904107ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:48:51Z"
    - latency: 2.419861ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:47:51Z"
    - latency: 2.500799ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:46:51Z"
    - latency: 2.378448ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:51Z"
    - latency: 2.162679ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-network-check-target-ip-10-0-141-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "69304"
    uid: db2a04d8-0489-4c3b-9d4f-ff088ccabb8e
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:51Z"
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252886ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 1.891034ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 2.245297ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 2.22703ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 2.458061ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:49:51Z"
    - latency: 2.144467ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:48:51Z"
    - latency: 2.252458ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:47:51Z"
    - latency: 2.268226ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:46:51Z"
    - latency: 2.346496ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:45:51Z"
    - latency: 2.413293ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-31.ec2.internal
      uid: 6931ceb0-6aa4-46d7-9d7c-243e5dd7ffe1
    resourceVersion: "70330"
    uid: cf05a0f1-9be2-4d95-8df6-a6f520768f47
  spec:
    sourcePod: network-check-source-6f8b768455-m42w5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:24:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:54:51Z"
    - latency: 2.057647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:54:51Z"
    - latency: 1.261312ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 1.861959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:53:51Z"
    - latency: 924.386µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 2.029324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:52:51Z"
    - latency: 957.163µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 1.697449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:51:51Z"
    - latency: 982.912µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:50:51Z"
    - latency: 1.796617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:50:51Z"
kind: List
metadata:
  resourceVersion: ""