apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63205"
    uid: 17063caa-c5ac-44bb-9c05-2d313c7702db
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:01:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 1.03468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 1.053732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 994.061µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 977.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:18Z"
    - latency: 990.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:18Z"
    - latency: 1.201504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:18Z"
    - latency: 982.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:18Z"
    - latency: 975.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:21:18Z"
    - latency: 1.117445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63763"
    uid: e5f830e0-0063-4109-bb97-c57704b1e742
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:00:18Z"
      message: 'load-balancer-api-external: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.356514ms
      message: 'load-balancer-api-external: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:18Z"
    - latency: 8.675021ms
      message: 'load-balancer-api-external: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:30:18Z"
    - latency: 4.400612ms
      message: 'load-balancer-api-external: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 9.445862ms
      message: 'load-balancer-api-external: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 3.447895ms
      message: 'load-balancer-api-external: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 8.449202ms
      message: 'load-balancer-api-external: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 4.609609ms
      message: 'load-balancer-api-external: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 8.761731ms
      message: 'load-balancer-api-external: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 5.962621ms
      message: 'load-balancer-api-external: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 8.575792ms
      message: 'load-balancer-api-external: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:26:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63764"
    uid: 35c6d910-71bb-4a2b-9ec3-62268fe4d9ce
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:00:18Z"
      message: 'load-balancer-api-internal: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.351077ms
      message: 'load-balancer-api-internal: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:18Z"
    - latency: 8.613081ms
      message: 'load-balancer-api-internal: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:30:18Z"
    - latency: 4.394581ms
      message: 'load-balancer-api-internal: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 9.381283ms
      message: 'load-balancer-api-internal: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 3.753388ms
      message: 'load-balancer-api-internal: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 8.462031ms
      message: 'load-balancer-api-internal: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 4.643973ms
      message: 'load-balancer-api-internal: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 8.851852ms
      message: 'load-balancer-api-internal: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 5.297064ms
      message: 'load-balancer-api-internal: tcp connection to a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 8.520046ms
      message: 'load-balancer-api-internal: resolved host name a8309c98fb2ba42708c893b908f4c2aa-dfe60b36d591b432.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:26:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-ip-10-0-130-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63204"
    uid: 2c16b7d1-d15b-467d-8183-0aa16ce617f2
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:01:18Z"
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.956381ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 2.557185ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 2.416711ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 2.45514ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 2.505259ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:18Z"
    - latency: 1.931786ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:18Z"
    - latency: 2.382944ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:18Z"
    - latency: 1.966954ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:18Z"
    - latency: 2.52047ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:21:18Z"
    - latency: 2.607244ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-ip-10-0-133-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63203"
    uid: 5bc8c65c-73f9-455f-9e9e-69dcec5e9aab
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:01:18Z"
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.39439ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 2.393421ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 2.404367ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 2.438535ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 2.455526ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:18Z"
    - latency: 2.024825ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:18Z"
    - latency: 2.274009ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:18Z"
    - latency: 2.377383ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:18Z"
    - latency: 2.343951ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:21:18Z"
    - latency: 2.476488ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-ip-10-0-140-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63202"
    uid: 191fd654-b2b8-4bc3-a205-f113edfcff6c
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:01:18Z"
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.084358ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 1.04161ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 1.150207ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 1.42013ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 882.686µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:18Z"
    - latency: 918.468µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:18Z"
    - latency: 935.892µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:18Z"
    - latency: 893.67µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:18Z"
    - latency: 1.170047ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:21:18Z"
    - latency: 1.049301ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:54:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 21408cac-8ef1-49b4-9706-3187a95501a0
    resourceVersion: "63762"
    uid: ff4563fd-c4ea-4b85-9e40-8fbe1f55240c
  spec:
    sourcePod: network-check-source-7cbc45fddc-9ttqt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:00:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.02µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:18Z"
    - latency: 2.133297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:30:18Z"
    - latency: 893.514µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 1.872669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:29:18Z"
    - latency: 1.334456ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 1.946523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:28:18Z"
    - latency: 809.407µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 1.766996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:27:18Z"
    - latency: 1.31992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:18Z"
    - latency: 2.060762ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:26:18Z"
kind: List
metadata:
  resourceVersion: ""