apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "154732"
    uid: 8f42f288-7133-4ef0-82e1-b50131f9296d
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:29:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.838µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 897.549µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 5.707997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 1.197165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:18Z"
    - latency: 1.238387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:18Z"
    - latency: 1.424936ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:18Z"
    - latency: 1.344524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:18Z"
    - latency: 979.736µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:18Z"
    - latency: 2.475965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:18Z"
    - latency: 1.135198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "155860"
    uid: 52e1a1af-5a13-4984-be6a-b3691f0b2cc2
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:28:18Z"
      message: 'load-balancer-api-external: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.8154ms
      message: 'load-balancer-api-external: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:34:18Z"
    - latency: 6.806526ms
      message: 'load-balancer-api-external: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:34:18Z"
    - latency: 15.840523ms
      message: 'load-balancer-api-external: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:33:18Z"
    - latency: 10.110326ms
      message: 'load-balancer-api-external: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:33:18Z"
    - latency: 16.574156ms
      message: 'load-balancer-api-external: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 8.816818ms
      message: 'load-balancer-api-external: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 17.692083ms
      message: 'load-balancer-api-external: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 7.351929ms
      message: 'load-balancer-api-external: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 32.05217ms
      message: 'load-balancer-api-external: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 58.971727ms
      message: 'load-balancer-api-external: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:30:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "155861"
    uid: cda19646-d6a3-4b14-b0ec-3233b7a7fa83
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:28:18Z"
      message: 'load-balancer-api-internal: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.83341ms
      message: 'load-balancer-api-internal: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:34:18Z"
    - latency: 6.886855ms
      message: 'load-balancer-api-internal: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:34:18Z"
    - latency: 14.656882ms
      message: 'load-balancer-api-internal: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:33:18Z"
    - latency: 10.195837ms
      message: 'load-balancer-api-internal: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:33:18Z"
    - latency: 16.421179ms
      message: 'load-balancer-api-internal: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 8.909541ms
      message: 'load-balancer-api-internal: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 17.631091ms
      message: 'load-balancer-api-internal: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 7.445921ms
      message: 'load-balancer-api-internal: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 31.710167ms
      message: 'load-balancer-api-internal: tcp connection to ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 53.697987ms
      message: 'load-balancer-api-internal: resolved host name ab8e4399e5ec647c7bd954992cc95294-ad1d325e65a4bf33.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:30:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-network-check-target-ip-10-0-128-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "154731"
    uid: 6d0eccd4-119b-4feb-9921-46ced4a80076
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:29:18Z"
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.114481ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 2.018437ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 6.089146ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 2.266656ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:18Z"
    - latency: 2.260808ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:18Z"
    - latency: 2.433576ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:18Z"
    - latency: 2.522631ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:18Z"
    - latency: 2.524996ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:18Z"
    - latency: 6.875034ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:18Z"
    - latency: 2.224031ms
      message: 'network-check-target-ip-10-0-128-181: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-network-check-target-ip-10-0-129-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "154730"
    uid: b3af06ff-a1e6-4a23-b0cb-8a8d54f95659
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:29:18Z"
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.12163ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 2.096309ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 6.636222ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 2.261351ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:18Z"
    - latency: 1.875979ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:18Z"
    - latency: 2.451219ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:18Z"
    - latency: 2.032831ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:18Z"
    - latency: 2.386572ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:18Z"
    - latency: 4.021316ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:18Z"
    - latency: 2.161284ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-network-check-target-ip-10-0-131-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "154729"
    uid: 75b182dc-1b2f-4284-8b63-faef3bb37a4e
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:29:18Z"
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.386µs
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 1.289325ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 13.389745ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 1.590223ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:18Z"
    - latency: 1.79139ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:18Z"
    - latency: 999.307µs
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:18Z"
    - latency: 1.802286ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:18Z"
    - latency: 1.403599ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:18Z"
    - latency: 4.256813ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:18Z"
    - latency: 1.093949ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-136-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-136.ec2.internal
      uid: e53d3374-eb38-4439-9fa2-b5ec23d48921
    resourceVersion: "155859"
    uid: 12c656d4-daf0-43b0-9c2b-32c778e44b8f
  spec:
    sourcePod: network-check-source-6f78d59f99-nwvwc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:28:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.236598ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:34:18Z"
    - latency: 1.958066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:34:18Z"
    - latency: 1.135288ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:33:18Z"
    - latency: 2.119906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:33:18Z"
    - latency: 1.086775ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 2.140726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:32:18Z"
    - latency: 995.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 2.139819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:31:18Z"
    - latency: 9.326609ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:18Z"
    - latency: 23.834008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:30:18Z"
kind: List
metadata:
  resourceVersion: ""