apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "54319"
    uid: 50e0b9ce-dacf-4d78-b9a3-0d83951b52b6
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:04:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.094437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 1.228954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 902.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 1.012393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:51Z"
    - latency: 1.023578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:51Z"
    - latency: 992.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:51Z"
    - latency: 994.222µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:51Z"
    - latency: 1.176845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:51Z"
    - latency: 922.939µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:51Z"
    - latency: 1.15297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "56029"
    uid: 5d613e70-6f05-47a4-bc81-2492150c77b6
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:03:51Z"
      message: 'load-balancer-api-external: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.088683ms
      message: 'load-balancer-api-external: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:27:51Z"
    - latency: 6.249077ms
      message: 'load-balancer-api-external: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:27:51Z"
    - latency: 4.337446ms
      message: 'load-balancer-api-external: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:26:51Z"
    - latency: 7.356125ms
      message: 'load-balancer-api-external: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:26:51Z"
    - latency: 4.636675ms
      message: 'load-balancer-api-external: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 6.060208ms
      message: 'load-balancer-api-external: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 3.743662ms
      message: 'load-balancer-api-external: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 8.017941ms
      message: 'load-balancer-api-external: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 4.620577ms
      message: 'load-balancer-api-external: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 7.33793ms
      message: 'load-balancer-api-external: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "56028"
    uid: e621b0ed-af74-46c2-bf87-01b382139c9a
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:03:51Z"
      message: 'load-balancer-api-internal: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.71564ms
      message: 'load-balancer-api-internal: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:27:51Z"
    - latency: 6.217981ms
      message: 'load-balancer-api-internal: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:27:51Z"
    - latency: 6.084507ms
      message: 'load-balancer-api-internal: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:26:51Z"
    - latency: 7.253495ms
      message: 'load-balancer-api-internal: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:26:51Z"
    - latency: 4.734891ms
      message: 'load-balancer-api-internal: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 6.044076ms
      message: 'load-balancer-api-internal: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 3.771405ms
      message: 'load-balancer-api-internal: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 7.98962ms
      message: 'load-balancer-api-internal: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 4.628222ms
      message: 'load-balancer-api-internal: tcp connection to a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 7.227492ms
      message: 'load-balancer-api-internal: resolved host name a5bac2fe6d26a45d898655521b7a6910-ec88a4ee31720635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-network-check-target-ip-10-0-130-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "54316"
    uid: fe612506-6d45-411d-af6a-764581f26c08
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:04:51Z"
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.156µs
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 1.04786ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 1.023323ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 1.157664ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:51Z"
    - latency: 1.031331ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:51Z"
    - latency: 1.431454ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:51Z"
    - latency: 1.638838ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:51Z"
    - latency: 1.05598ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:51Z"
    - latency: 1.17457ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:51Z"
    - latency: 1.021088ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-network-check-target-ip-10-0-138-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "54318"
    uid: d00db9e6-db5b-408e-a753-dea2e073417c
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:04:51Z"
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.476351ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 2.570703ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 2.371398ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 2.54229ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:51Z"
    - latency: 2.487897ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:51Z"
    - latency: 2.847094ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:51Z"
    - latency: 2.608845ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:51Z"
    - latency: 2.377425ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:51Z"
    - latency: 2.102725ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:51Z"
    - latency: 2.226532ms
      message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-network-check-target-ip-10-0-140-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "54317"
    uid: d52f53b9-bd0a-46c7-b4c7-da941a0c52c3
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:04:51Z"
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155615ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 2.507243ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 2.186488ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 2.670196ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:51Z"
    - latency: 2.525201ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:51Z"
    - latency: 2.676158ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:51Z"
    - latency: 2.669551ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:51Z"
    - latency: 2.654413ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:51Z"
    - latency: 2.267894ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:51Z"
    - latency: 2.616497ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-195-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-195.ec2.internal
      uid: fcc6afc6-3af8-43b4-8dad-c7f67489b003
    resourceVersion: "56027"
    uid: ed2cc82b-6709-46d2-aff4-cd0d6f9cfe01
  spec:
    sourcePod: network-check-source-6f8b768455-5lhhq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:03:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.219µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:27:51Z"
    - latency: 1.820211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:27:51Z"
    - latency: 1.011462ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:26:51Z"
    - latency: 1.711808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:26:51Z"
    - latency: 1.135897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 1.99238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:25:51Z"
    - latency: 961.007µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 2.001705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:24:51Z"
    - latency: 1.024249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:51Z"
    - latency: 2.227931ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:23:51Z"
kind: List
metadata:
  resourceVersion: ""