apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "53085"
    uid: 85a4fd29-ed24-4e30-b759-6e86861527ce
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:04:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 995.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 1.062737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 1.111429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 1.106818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:28:23Z"
    - latency: 1.302038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:27:23Z"
    - latency: 1.110829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:26:23Z"
    - latency: 1.017579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:25:23Z"
    - latency: 871.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:24:23Z"
    - latency: 1.271883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "54237"
    uid: 24bde6f1-306b-48c6-bc94-26db435d2469
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:03:23Z"
      message: 'load-balancer-api-external: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.062767ms
      message: 'load-balancer-api-external: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:33:23Z"
    - latency: 8.391313ms
      message: 'load-balancer-api-external: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:33:23Z"
    - latency: 5.236943ms
      message: 'load-balancer-api-external: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 8.598683ms
      message: 'load-balancer-api-external: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 4.82775ms
      message: 'load-balancer-api-external: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 8.310087ms
      message: 'load-balancer-api-external: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 4.021335ms
      message: 'load-balancer-api-external: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 11.274417ms
      message: 'load-balancer-api-external: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 6.101482ms
      message: 'load-balancer-api-external: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 7.846305ms
      message: 'load-balancer-api-external: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:29:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "54236"
    uid: 14acc961-6750-467f-8504-64ecdac3760a
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:03:23Z"
      message: 'load-balancer-api-internal: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.246611ms
      message: 'load-balancer-api-internal: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:33:23Z"
    - latency: 8.280917ms
      message: 'load-balancer-api-internal: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:33:23Z"
    - latency: 5.191631ms
      message: 'load-balancer-api-internal: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 8.573715ms
      message: 'load-balancer-api-internal: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 4.857928ms
      message: 'load-balancer-api-internal: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 8.288845ms
      message: 'load-balancer-api-internal: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 5.086392ms
      message: 'load-balancer-api-internal: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 11.192724ms
      message: 'load-balancer-api-internal: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 5.897708ms
      message: 'load-balancer-api-internal: tcp connection to a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 7.911721ms
      message: 'load-balancer-api-internal: resolved host name a094a18098eb4497c928a0d6e3fa73cb-d803c1b88e19a4fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:29:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-network-check-target-ip-10-0-128-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "53083"
    uid: 5ac99718-8d40-4867-bc52-e0cd4ea33be5
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:04:23Z"
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.166949ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 2.419461ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 2.45208ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 2.492465ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 2.342154ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:28:23Z"
    - latency: 2.190358ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:27:23Z"
    - latency: 2.451091ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:26:23Z"
    - latency: 2.270446ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:25:23Z"
    - latency: 2.383596ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:24:23Z"
    - latency: 2.339399ms
      message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-network-check-target-ip-10-0-133-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "53082"
    uid: 70a87c32-d083-465a-b7a7-57107c777e66
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:04:23Z"
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039476ms
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 953.879µs
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 1.237283ms
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 912.445µs
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 1.384472ms
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:28:23Z"
    - latency: 852.031µs
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:27:23Z"
    - latency: 1.33065ms
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:26:23Z"
    - latency: 1.494659ms
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:25:23Z"
    - latency: 938.005µs
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:24:23Z"
    - latency: 879.876µs
      message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-network-check-target-ip-10-0-140-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "53084"
    uid: be34c4f0-b10d-41f0-835f-169864c9fd15
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:04:23Z"
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.35131ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 2.519959ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 2.553004ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 2.501456ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 2.181563ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:28:23Z"
    - latency: 2.582952ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:27:23Z"
    - latency: 2.771851ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:26:23Z"
    - latency: 2.441002ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:25:23Z"
    - latency: 2.36024ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:24:23Z"
    - latency: 2.878906ms
      message: 'network-check-target-ip-10-0-140-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-54.ec2.internal
      uid: 9039319f-1024-4cca-9346-3df708e506b3
    resourceVersion: "54234"
    uid: eb4129e7-b05b-4751-b793-826a3ccdd86f
  spec:
    sourcePod: network-check-source-989f8b8dc-dn66g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:03:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.185498ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:33:23Z"
    - latency: 1.840844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:33:23Z"
    - latency: 1.232223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 1.790051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:32:23Z"
    - latency: 868.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 1.720189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:31:23Z"
    - latency: 1.114364ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 1.630853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:30:23Z"
    - latency: 965.846µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:29:23Z"
    - latency: 1.762688ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:29:23Z"
kind: List
metadata:
  resourceVersion: ""