apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53305"
    uid: 40ba61a9-956d-46ad-a524-1372a60105bb
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:46:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 779.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 881.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 815.63µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 800.886µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 922.112µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:58:06Z"
    - latency: 1.023155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:06Z"
    - latency: 1.705545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:06Z"
    - latency: 1.02464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:06Z"
    - latency: 859.354µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53306"
    uid: fbc48ce4-aadf-4249-9ceb-ed825aeb7b08
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:06Z"
      message: 'load-balancer-api-external: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.207946ms
      message: 'load-balancer-api-external: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 6.703029ms
      message: 'load-balancer-api-external: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 3.954101ms
      message: 'load-balancer-api-external: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 6.791873ms
      message: 'load-balancer-api-external: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 5.011388ms
      message: 'load-balancer-api-external: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 7.30628ms
      message: 'load-balancer-api-external: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 5.6062ms
      message: 'load-balancer-api-external: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 6.606059ms
      message: 'load-balancer-api-external: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 5.210231ms
      message: 'load-balancer-api-external: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 6.807978ms
      message: 'load-balancer-api-external: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:59:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53307"
    uid: 0782ae8a-0fa7-4de6-bf0b-d06572a72997
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:06Z"
      message: 'load-balancer-api-internal: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.223506ms
      message: 'load-balancer-api-internal: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 6.817079ms
      message: 'load-balancer-api-internal: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 3.967046ms
      message: 'load-balancer-api-internal: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 6.943927ms
      message: 'load-balancer-api-internal: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 4.939753ms
      message: 'load-balancer-api-internal: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 7.382074ms
      message: 'load-balancer-api-internal: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 5.598501ms
      message: 'load-balancer-api-internal: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 6.755675ms
      message: 'load-balancer-api-internal: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 5.21142ms
      message: 'load-balancer-api-internal: tcp connection to a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 6.857808ms
      message: 'load-balancer-api-internal: resolved host name a2ba61fdc0bcb408a8baa549b18a5fdd-1d79fd7f1516f9d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:59:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-129-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53302"
    uid: 67a9e10b-7342-4df3-ad42-d103167702f0
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:46:06Z"
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.749709ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 2.090715ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 1.789135ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 1.771167ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 1.644111ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 1.630987ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:58:06Z"
    - latency: 1.920485ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:06Z"
    - latency: 2.041561ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:06Z"
    - latency: 1.853522ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:06Z"
    - latency: 1.870193ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-137-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53303"
    uid: 948467a9-2de2-4c17-a880-f82bdc5399eb
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:46:06Z"
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.114029ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 2.118232ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 2.224707ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 2.078991ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 2.136133ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 2.083838ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:58:06Z"
    - latency: 2.179831ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:06Z"
    - latency: 2.126047ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:06Z"
    - latency: 2.197863ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:06Z"
    - latency: 1.97573ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-138-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53301"
    uid: 1f254fcf-ec3c-4b46-9752-aec1696249f1
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:46:06Z"
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.83µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 920.418µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 724.513µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 887.623µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 828.592µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 993.965µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:58:06Z"
    - latency: 1.333948ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:06Z"
    - latency: 747.487µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:06Z"
    - latency: 934.122µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:06Z"
    - latency: 853.677µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:39:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 208ef5f0-bf05-40bf-b5b6-72ab2d4aeb6a
    resourceVersion: "53304"
    uid: 4d1f7789-f525-425f-9d56-c894c95bce8c
  spec:
    sourcePod: network-check-source-7d88cb55d8-dq99c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 735.806µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 1.79004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:03:06Z"
    - latency: 879.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 1.993366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:02:06Z"
    - latency: 795.449µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 2.484463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:01:06Z"
    - latency: 935.252µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 1.656446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:00:06Z"
    - latency: 758.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:59:06Z"
    - latency: 1.966324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:59:06Z"
kind: List
metadata:
  resourceVersion: ""