apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "49811"
    uid: 6508a703-065f-44eb-9f5d-7208a0d7824f
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30: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.730156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 922.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 949.346µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 954.047µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 826.712µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:27Z"
    - latency: 1.105171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:27Z"
    - latency: 1.119721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:27Z"
    - latency: 1.221313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:27Z"
    - latency: 1.2834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:27Z"
    - latency: 1.052049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "50411"
    uid: 6a0ba262-ebd9-420c-9dd0-0f8c08e873e6
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:29:27Z"
      message: 'load-balancer-api-external: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.259465ms
      message: 'load-balancer-api-external: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:59:27Z"
    - latency: 8.184695ms
      message: 'load-balancer-api-external: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:59:27Z"
    - latency: 5.498366ms
      message: 'load-balancer-api-external: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 6.986811ms
      message: 'load-balancer-api-external: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 3.867597ms
      message: 'load-balancer-api-external: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 8.069725ms
      message: 'load-balancer-api-external: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 5.227833ms
      message: 'load-balancer-api-external: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 8.407992ms
      message: 'load-balancer-api-external: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 5.449195ms
      message: 'load-balancer-api-external: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 7.880518ms
      message: 'load-balancer-api-external: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:55:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "50410"
    uid: 7717c6f1-c6a5-47e5-a514-bdbbd952a6c0
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:29:27Z"
      message: 'load-balancer-api-internal: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.23355ms
      message: 'load-balancer-api-internal: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:59:27Z"
    - latency: 8.097256ms
      message: 'load-balancer-api-internal: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:59:27Z"
    - latency: 5.232672ms
      message: 'load-balancer-api-internal: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 7.066136ms
      message: 'load-balancer-api-internal: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 4.565804ms
      message: 'load-balancer-api-internal: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 8.156877ms
      message: 'load-balancer-api-internal: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 5.210439ms
      message: 'load-balancer-api-internal: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 8.500938ms
      message: 'load-balancer-api-internal: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 5.425273ms
      message: 'load-balancer-api-internal: tcp connection to a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 7.926932ms
      message: 'load-balancer-api-internal: resolved host name a1806ba49b5514ba59f0b74c12bb0c73-22c0f10b40e96de3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:55:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-ip-10-0-131-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "49808"
    uid: 179514ca-4b5f-4161-bfb5-a51a321e3aa9
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30:27Z"
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.584µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 909.681µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 911.767µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 1.600515ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 868.607µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:27Z"
    - latency: 1.46499ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:27Z"
    - latency: 1.00921ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:27Z"
    - latency: 1.344547ms
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:27Z"
    - latency: 972.025µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:27Z"
    - latency: 908.912µs
      message: 'network-check-target-ip-10-0-131-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-ip-10-0-135-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "49809"
    uid: d62f53ea-96a8-4ce5-851d-b91f979d596d
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30:27Z"
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.274721ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 2.216206ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 2.35158ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 2.34566ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 2.210174ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:27Z"
    - latency: 2.764528ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:27Z"
    - latency: 2.191586ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:27Z"
    - latency: 2.531927ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:27Z"
    - latency: 2.263726ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:27Z"
    - latency: 2.254965ms
      message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-ip-10-0-141-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "49810"
    uid: e8ec360b-7e89-44b9-94cc-d523fb0dada6
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30:27Z"
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.405195ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 2.001703ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 2.290719ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 2.276707ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 2.251317ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:27Z"
    - latency: 2.693019ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:27Z"
    - latency: 2.260869ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:27Z"
    - latency: 2.456252ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:27Z"
    - latency: 2.321158ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:27Z"
    - latency: 2.331295ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:23:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-141-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-141.ec2.internal
      uid: 88b8e200-82e5-4f19-a370-109e55a6703e
    resourceVersion: "50409"
    uid: 711afeae-1d4f-411b-af07-caa8a732c335
  spec:
    sourcePod: network-check-source-989f8b8dc-mph84
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:29:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.32µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:59:27Z"
    - latency: 1.663821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:59:27Z"
    - latency: 907.844µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 2.461085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:58:27Z"
    - latency: 880.494µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 1.649509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:57:27Z"
    - latency: 793.201µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 1.673763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:56:27Z"
    - latency: 945.574µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:55:27Z"
    - latency: 1.846554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:55:27Z"
kind: List
metadata:
  resourceVersion: ""