apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63870"
    uid: af43779a-ecd7-40d9-8f48-9c6dd6af67a9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:12:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 845.499µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 1.382093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 831.048µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 968.628µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 826.456µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 875.097µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:42:52Z"
    - latency: 807.526µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:41:52Z"
    - latency: 944.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:40:52Z"
    - latency: 1.120788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:39:52Z"
    - latency: 925.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63872"
    uid: ad7cbb3a-4781-4a83-8d7d-387018ddb2f0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:11:52Z"
      message: 'load-balancer-api-external: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.278188ms
      message: 'load-balancer-api-external: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 6.892114ms
      message: 'load-balancer-api-external: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 4.87332ms
      message: 'load-balancer-api-external: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 8.610416ms
      message: 'load-balancer-api-external: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 4.485644ms
      message: 'load-balancer-api-external: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 7.336366ms
      message: 'load-balancer-api-external: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 4.758975ms
      message: 'load-balancer-api-external: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 7.618397ms
      message: 'load-balancer-api-external: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 3.467621ms
      message: 'load-balancer-api-external: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 8.235915ms
      message: 'load-balancer-api-external: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:43:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63871"
    uid: 8bee4804-dd86-472b-b029-3bcc537c07a0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:11:52Z"
      message: 'load-balancer-api-internal: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.28071ms
      message: 'load-balancer-api-internal: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 6.936678ms
      message: 'load-balancer-api-internal: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 4.859529ms
      message: 'load-balancer-api-internal: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 8.586895ms
      message: 'load-balancer-api-internal: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 4.019826ms
      message: 'load-balancer-api-internal: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 7.263387ms
      message: 'load-balancer-api-internal: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 4.785662ms
      message: 'load-balancer-api-internal: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 7.670773ms
      message: 'load-balancer-api-internal: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 5.159495ms
      message: 'load-balancer-api-internal: tcp connection to a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 8.169819ms
      message: 'load-balancer-api-internal: resolved host name a62dad94539ad4b2f913fcf4a92c496c-0fa8a40ce9fbecab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:43:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-network-check-target-ip-10-0-128-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63868"
    uid: 5332b22a-7cbd-44d0-b471-a8c1d121e586
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:12:52Z"
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.189047ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 3.025399ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 2.355007ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 2.384896ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 2.445811ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 2.299068ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:42:52Z"
    - latency: 2.518486ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:41:52Z"
    - latency: 2.33509ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:40:52Z"
    - latency: 2.809415ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:39:52Z"
    - latency: 2.47037ms
      message: 'network-check-target-ip-10-0-128-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-network-check-target-ip-10-0-133-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63867"
    uid: 36ae322c-5c56-405a-95a7-519d177119b8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:12:52Z"
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.395265ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 2.408821ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 2.281482ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 2.300147ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 2.245959ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 2.367506ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:42:52Z"
    - latency: 2.243012ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:41:52Z"
    - latency: 2.304065ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:40:52Z"
    - latency: 2.409703ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:39:52Z"
    - latency: 2.231615ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-network-check-target-ip-10-0-135-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63866"
    uid: b8b4f77f-8a07-4bf4-ba6b-4c852502258e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:12:52Z"
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.436584ms
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 829.902µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 1.048513ms
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 829.063µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 800.283µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 785.628µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:42:52Z"
    - latency: 773.97µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:41:52Z"
    - latency: 851.686µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:40:52Z"
    - latency: 1.48932ms
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:39:52Z"
    - latency: 956.388µs
      message: 'network-check-target-ip-10-0-135-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:38:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T05:05:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-196.ec2.internal
      uid: 9554ecd0-76e9-4fc1-ab9a-76b2c6b2b185
    resourceVersion: "63869"
    uid: 64b4ffa5-f143-438e-b37c-54932f4c41e0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9qgn8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T05:11:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 1.803198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:47:52Z"
    - latency: 916.398µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 1.701389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:46:52Z"
    - latency: 834.911µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 1.655639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:45:52Z"
    - latency: 1.000865ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 1.631926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:44:52Z"
    - latency: 1.081107ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T05:43:52Z"
    - latency: 1.629306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T05:43:52Z"
kind: List
metadata:
  resourceVersion: ""