apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60772"
    uid: 37dcf7f1-abf1-49ef-afbd-e8f298d1ca27
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:35:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.168448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 1.665946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 1.288091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 967.21µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 1.03856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 890.692µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:46Z"
    - latency: 1.112038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:46Z"
    - latency: 1.278533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:46Z"
    - latency: 875.691µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:46Z"
    - latency: 990.678µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60774"
    uid: 0ac91248-ce0b-479e-a94c-d36f55f120d1
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:34:46Z"
      message: 'load-balancer-api-external: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.441593ms
      message: 'load-balancer-api-external: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 7.843273ms
      message: 'load-balancer-api-external: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 8.412049ms
      message: 'load-balancer-api-external: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 9.589766ms
      message: 'load-balancer-api-external: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 11.469286ms
      message: 'load-balancer-api-external: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 8.261886ms
      message: 'load-balancer-api-external: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 4.612844ms
      message: 'load-balancer-api-external: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 7.264338ms
      message: 'load-balancer-api-external: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 6.215465ms
      message: 'load-balancer-api-external: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 8.695705ms
      message: 'load-balancer-api-external: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:06:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60773"
    uid: ac739050-b062-4a39-9588-b7bd87556a59
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:34:46Z"
      message: 'load-balancer-api-internal: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.380048ms
      message: 'load-balancer-api-internal: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 7.888334ms
      message: 'load-balancer-api-internal: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 4.594096ms
      message: 'load-balancer-api-internal: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 9.452264ms
      message: 'load-balancer-api-internal: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 11.50588ms
      message: 'load-balancer-api-internal: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 8.169009ms
      message: 'load-balancer-api-internal: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 5.337512ms
      message: 'load-balancer-api-internal: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 7.148291ms
      message: 'load-balancer-api-internal: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 5.004358ms
      message: 'load-balancer-api-internal: tcp connection to a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 8.567647ms
      message: 'load-balancer-api-internal: resolved host name a7e05988fc0e34c29b46ba8f03c82e83-d922fb86d4dab183.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:06:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-ip-10-0-128-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60771"
    uid: b795e319-8d4a-4b37-a708-c88630557e12
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:35:46Z"
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079882ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 2.146042ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 2.275246ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 2.29795ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 2.252615ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 2.32671ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:46Z"
    - latency: 2.340445ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:46Z"
    - latency: 2.164874ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:46Z"
    - latency: 2.358326ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:46Z"
    - latency: 1.712827ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-ip-10-0-131-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60768"
    uid: 7052f830-117b-49f9-9cb0-2d5bbd0465cf
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:35:46Z"
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092552ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 997.477µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 1.035624ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 1.175326ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 955.24µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 1.558036ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:46Z"
    - latency: 1.100495ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:46Z"
    - latency: 1.047555ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:46Z"
    - latency: 895.281µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:46Z"
    - latency: 991.262µs
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-ip-10-0-142-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60769"
    uid: a4fdb2c6-50f4-4433-9dd2-d626ce4ca461
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:35:46Z"
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950139ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 2.231374ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 1.970081ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 2.219797ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 1.936046ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 2.219362ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:46Z"
    - latency: 2.274815ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:46Z"
    - latency: 2.002267ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:46Z"
    - latency: 2.007836ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:46Z"
    - latency: 1.500568ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-94.ec2.internal
      uid: fa5a4114-b464-4471-ace6-46f50dd27b01
    resourceVersion: "60770"
    uid: 1dd0c707-6f90-4241-99dd-8f71374e86a4
  spec:
    sourcePod: network-check-source-869dcfcdcd-cq4df
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T16:34:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 1.974127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:10:46Z"
    - latency: 938.025µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 1.899528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:09:46Z"
    - latency: 1.028788ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 2.208134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:08:46Z"
    - latency: 919.205µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 2.247762ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:07:46Z"
    - latency: 1.061419ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:46Z"
    - latency: 1.961517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:06:46Z"
kind: List
metadata:
  resourceVersion: ""