apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "73218"
    uid: af4f2e94-7dfa-4cfd-86a5-24250e51cd2b
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.047µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 1.591501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 831.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:45:52Z"
    - latency: 1.231777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:44:52Z"
    - latency: 858.884µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:43:52Z"
    - latency: 889.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:42:52Z"
    - latency: 879.235µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:41:52Z"
    - latency: 949.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:40:52Z"
    - latency: 864.022µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:39:52Z"
    - latency: 1.146916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "75955"
    uid: aeb24215-1426-48e7-ac9b-a108db5045f3
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:50:52Z"
      message: 'load-balancer-api-external: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.776599ms
      message: 'load-balancer-api-external: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:50:52Z"
    - latency: 7.113149ms
      message: 'load-balancer-api-external: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:50:52Z"
    - latency: 3.564659ms
      message: 'load-balancer-api-external: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:49:52Z"
    - latency: 7.046025ms
      message: 'load-balancer-api-external: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:49:52Z"
    - latency: 4.621744ms
      message: 'load-balancer-api-external: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:48:52Z"
    - latency: 7.342413ms
      message: 'load-balancer-api-external: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:48:52Z"
    - latency: 4.404218ms
      message: 'load-balancer-api-external: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 6.484465ms
      message: 'load-balancer-api-external: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 4.860036ms
      message: 'load-balancer-api-external: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 7.475414ms
      message: 'load-balancer-api-external: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:46:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "75954"
    uid: 4145c2f5-06f0-40f7-b7c0-f52b98431e58
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:50:52Z"
      message: 'load-balancer-api-internal: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.407407ms
      message: 'load-balancer-api-internal: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:50:52Z"
    - latency: 7.042854ms
      message: 'load-balancer-api-internal: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:50:52Z"
    - latency: 4.23218ms
      message: 'load-balancer-api-internal: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:49:52Z"
    - latency: 7.073235ms
      message: 'load-balancer-api-internal: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:49:52Z"
    - latency: 4.602708ms
      message: 'load-balancer-api-internal: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:48:52Z"
    - latency: 7.277258ms
      message: 'load-balancer-api-internal: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:48:52Z"
    - latency: 4.653906ms
      message: 'load-balancer-api-internal: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 6.464761ms
      message: 'load-balancer-api-internal: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 4.815698ms
      message: 'load-balancer-api-internal: tcp connection to a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 7.504419ms
      message: 'load-balancer-api-internal: resolved host name a0627cfe6eed54756a599ffd0c102765-1c19c42f3666b5fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:46:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-136-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "73219"
    uid: 3695fe9e-120d-4d5f-8d80-f51d2e3a01ed
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:52Z"
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 817.36µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 798.974µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 1.017569ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:45:52Z"
    - latency: 876.156µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:44:52Z"
    - latency: 773.111µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:43:52Z"
    - latency: 830.432µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:42:52Z"
    - latency: 1.249952ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:41:52Z"
    - latency: 1.302101ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:40:52Z"
    - latency: 814.619µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:39:52Z"
    - latency: 900.989µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-140-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "73216"
    uid: 8c097a64-0d76-4e06-9b97-6f4e4843ebe5
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:52Z"
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252635ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 2.180903ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 2.084907ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:45:52Z"
    - latency: 2.371178ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:44:52Z"
    - latency: 2.417497ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:43:52Z"
    - latency: 2.017263ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:42:52Z"
    - latency: 2.416388ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:41:52Z"
    - latency: 2.28594ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:40:52Z"
    - latency: 2.310317ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:39:52Z"
    - latency: 2.17465ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-141-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "73217"
    uid: 7bb691d9-d560-4ccc-b99a-656088944753
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:52Z"
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.01592ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 2.194579ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 2.103474ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:45:52Z"
    - latency: 2.047774ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:44:52Z"
    - latency: 2.227057ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:43:52Z"
    - latency: 2.652886ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:42:52Z"
    - latency: 2.325349ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:41:52Z"
    - latency: 2.178311ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:40:52Z"
    - latency: 2.204563ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:39:52Z"
    - latency: 2.118482ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:44:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: bb940b6e-4be1-4af8-9d2b-476e151ffa14
    resourceVersion: "75953"
    uid: ccc82f6d-bf2e-4cbc-a4d1-4aa371be6444
  spec:
    sourcePod: network-check-source-7cbc45fddc-pw2bg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:50:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.99µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:50:52Z"
    - latency: 1.64877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:50:52Z"
    - latency: 823.392µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:49:52Z"
    - latency: 1.604952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:49:52Z"
    - latency: 784.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:48:52Z"
    - latency: 2.19555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:48:52Z"
    - latency: 993.031µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 1.839621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:47:52Z"
    - latency: 713.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:46:52Z"
    - latency: 2.177277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:46:52Z"
kind: List
metadata:
  resourceVersion: ""