apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "53421"
    uid: 848785bd-11e6-4d50-899c-7591587a2fb5
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:59:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.116µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 993.896µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 919.226µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 946.724µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 849.151µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:23:00Z"
    - latency: 887.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:22:00Z"
    - latency: 1.045307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:21:00Z"
    - latency: 786.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:20:00Z"
    - latency: 925.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:19:00Z"
    - latency: 863.699µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "54431"
    uid: 1e540680-e663-4a8b-b264-04662b05ba76
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:58:00Z"
      message: 'load-balancer-api-external: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.519905ms
      message: 'load-balancer-api-external: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:28:00Z"
    - latency: 8.390369ms
      message: 'load-balancer-api-external: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:28:00Z"
    - latency: 7.913753ms
      message: 'load-balancer-api-external: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 7.825391ms
      message: 'load-balancer-api-external: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 3.623029ms
      message: 'load-balancer-api-external: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 10.020573ms
      message: 'load-balancer-api-external: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 5.962909ms
      message: 'load-balancer-api-external: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 12.60075ms
      message: 'load-balancer-api-external: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 5.929299ms
      message: 'load-balancer-api-external: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 11.940024ms
      message: 'load-balancer-api-external: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "54430"
    uid: 3001fdbc-8bed-4fbb-ba32-08f30659486e
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:58:00Z"
      message: 'load-balancer-api-internal: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.472816ms
      message: 'load-balancer-api-internal: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:28:00Z"
    - latency: 8.495712ms
      message: 'load-balancer-api-internal: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:28:00Z"
    - latency: 13.225699ms
      message: 'load-balancer-api-internal: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 7.87009ms
      message: 'load-balancer-api-internal: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 4.617828ms
      message: 'load-balancer-api-internal: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 9.98406ms
      message: 'load-balancer-api-internal: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 5.917434ms
      message: 'load-balancer-api-internal: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 12.645579ms
      message: 'load-balancer-api-internal: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 4.330812ms
      message: 'load-balancer-api-internal: tcp connection to a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 11.975282ms
      message: 'load-balancer-api-internal: resolved host name a1d19c0cbcb6b41559e2c7d59379b502-3c57fb1545cffc2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-ip-10-0-129-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "53418"
    uid: 2b46e21a-52e7-439f-84e2-075f2fc5c160
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:59:00Z"
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.505788ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 2.346423ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 2.578144ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 2.568412ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 2.208311ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:23:00Z"
    - latency: 2.597696ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:22:00Z"
    - latency: 2.348886ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:21:00Z"
    - latency: 2.223235ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:20:00Z"
    - latency: 2.423844ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:19:00Z"
    - latency: 2.003545ms
      message: 'network-check-target-ip-10-0-129-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-ip-10-0-136-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "53420"
    uid: 7c8234a9-9268-4423-a3e0-470d715b7b77
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:59:00Z"
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.102184ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 779.707µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 977.376µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 894.828µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 1.130674ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:23:00Z"
    - latency: 1.330888ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:22:00Z"
    - latency: 954.086µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:21:00Z"
    - latency: 974.043µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:20:00Z"
    - latency: 965.039µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:19:00Z"
    - latency: 865.638µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-ip-10-0-138-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "53419"
    uid: d245e49f-ba8a-4ac3-9298-f08e1fdf2dcc
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:59:00Z"
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346676ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 2.25049ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 2.314542ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 2.359151ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 1.900871ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:23:00Z"
    - latency: 2.533149ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:22:00Z"
    - latency: 2.333551ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:21:00Z"
    - latency: 2.19191ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:20:00Z"
    - latency: 2.35008ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:19:00Z"
    - latency: 1.957472ms
      message: 'network-check-target-ip-10-0-138-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:51:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 302dcd60-2365-44fc-940e-4dec8008fdde
    resourceVersion: "54429"
    uid: 2e05d6bd-f59b-49ed-826f-0fbab9539ae9
  spec:
    sourcePod: network-check-source-989f8b8dc-2lxt4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:58:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.201µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:28:00Z"
    - latency: 1.727845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:28:00Z"
    - latency: 927.062µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 2.000641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:27:00Z"
    - latency: 1.169864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 1.782691ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:26:00Z"
    - latency: 906.037µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 1.76753ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:25:00Z"
    - latency: 770.372µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:24:00Z"
    - latency: 1.910444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:24:00Z"
kind: List
metadata:
  resourceVersion: ""