apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "55160"
    uid: 5c9009e1-55f0-407d-966f-24bb107612eb
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.077308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 1.205476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 832.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 1.26699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 1.465627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:25Z"
    - latency: 873.338µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:25Z"
    - latency: 1.004431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:25Z"
    - latency: 1.125027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:25Z"
    - latency: 1.085103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:25Z"
    - latency: 907.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "56083"
    uid: 66d950f0-9e12-44d5-a664-41e979d189b5
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:01:25Z"
      message: 'load-balancer-api-external: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.471246ms
      message: 'load-balancer-api-external: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:25Z"
    - latency: 7.564774ms
      message: 'load-balancer-api-external: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:31:25Z"
    - latency: 4.031997ms
      message: 'load-balancer-api-external: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 6.497413ms
      message: 'load-balancer-api-external: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 4.877299ms
      message: 'load-balancer-api-external: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 6.876531ms
      message: 'load-balancer-api-external: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 5.53668ms
      message: 'load-balancer-api-external: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 6.741885ms
      message: 'load-balancer-api-external: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 4.081325ms
      message: 'load-balancer-api-external: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 6.924217ms
      message: 'load-balancer-api-external: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:27:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "56084"
    uid: 7b8452c5-3fa0-4200-9a20-47b9270fbec4
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:01:25Z"
      message: 'load-balancer-api-internal: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.548064ms
      message: 'load-balancer-api-internal: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:25Z"
    - latency: 7.613878ms
      message: 'load-balancer-api-internal: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:31:25Z"
    - latency: 4.012047ms
      message: 'load-balancer-api-internal: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 6.399029ms
      message: 'load-balancer-api-internal: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 4.889596ms
      message: 'load-balancer-api-internal: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 6.823326ms
      message: 'load-balancer-api-internal: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 5.595335ms
      message: 'load-balancer-api-internal: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 6.62007ms
      message: 'load-balancer-api-internal: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 4.338114ms
      message: 'load-balancer-api-internal: tcp connection to a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 6.843228ms
      message: 'load-balancer-api-internal: resolved host name a221d84b0a4a044debb928d1db59013c-293e08a21c30d998.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:27:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-network-check-target-ip-10-0-130-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "55159"
    uid: 87689c28-26ee-4ca6-804f-d75426cc62bf
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:25Z"
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.316677ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 2.152098ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 2.186522ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 2.205158ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 2.30592ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:25Z"
    - latency: 2.247232ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:25Z"
    - latency: 2.274835ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:25Z"
    - latency: 2.222996ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:25Z"
    - latency: 2.376911ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:25Z"
    - latency: 2.10456ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-network-check-target-ip-10-0-137-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "55158"
    uid: b076cac2-c933-46c2-8648-3f6db9d862a2
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:25Z"
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.182µs
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 996.446µs
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 794.023µs
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 1.338319ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 975.805µs
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:25Z"
    - latency: 1.258806ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:25Z"
    - latency: 1.008426ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:25Z"
    - latency: 1.321001ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:25Z"
    - latency: 1.550044ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:25Z"
    - latency: 852.322µs
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-network-check-target-ip-10-0-143-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "55157"
    uid: 19d44e2d-2f5f-4587-b90d-7c89a2d7615b
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:25Z"
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.036392ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 2.160562ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 1.857043ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 2.061695ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 1.704313ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:25Z"
    - latency: 2.100521ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:25Z"
    - latency: 1.996793ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:25Z"
    - latency: 2.128129ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:25Z"
    - latency: 2.017951ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:25Z"
    - latency: 1.818958ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-196.ec2.internal
      uid: 8f51798d-653b-4d0f-9632-5446dc6fe6fe
    resourceVersion: "56082"
    uid: 3b06f776-04e8-4f45-95a6-54e1ce56b6de
  spec:
    sourcePod: network-check-source-989f8b8dc-mrqrw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:01:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:25Z"
    - latency: 1.685557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:31:25Z"
    - latency: 926.398µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 1.826059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:30:25Z"
    - latency: 1.392736ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 1.882154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:29:25Z"
    - latency: 772.849µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 1.577978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:28:25Z"
    - latency: 817.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:25Z"
    - latency: 1.974218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:27:25Z"
kind: List
metadata:
  resourceVersion: ""