apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "31529"
    uid: f0b8adf1-379f-4406-8ff6-00b8754e980e
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:14:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.984096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:21:56Z"
    - latency: 937.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:20:56Z"
    - latency: 849.305µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 1.176464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 817.999µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 1.19306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 1.011708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 1.167736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:14:56Z"
    - latency: 974.279µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:13:56Z"
    - latency: 870.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "29692"
    uid: 98737132-ed0d-4ad2-83bf-11663f3f63d5
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:13:56Z"
      message: 'load-balancer-api-external: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.277418ms
      message: 'load-balancer-api-external: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 12.061989ms
      message: 'load-balancer-api-external: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 5.714857ms
      message: 'load-balancer-api-external: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 6.941618ms
      message: 'load-balancer-api-external: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 5.589156ms
      message: 'load-balancer-api-external: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 12.306306ms
      message: 'load-balancer-api-external: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 5.000622ms
      message: 'load-balancer-api-external: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 7.949427ms
      message: 'load-balancer-api-external: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 6.769583ms
      message: 'load-balancer-api-external: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 6.376087ms
      message: 'load-balancer-api-external: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:15:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "29693"
    uid: f69c3d5a-abf6-4e1b-9c9b-327f4c48eab7
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:13:56Z"
      message: 'load-balancer-api-internal: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.769776ms
      message: 'load-balancer-api-internal: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 12.229661ms
      message: 'load-balancer-api-internal: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 5.708126ms
      message: 'load-balancer-api-internal: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 6.977328ms
      message: 'load-balancer-api-internal: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 5.57956ms
      message: 'load-balancer-api-internal: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 12.392151ms
      message: 'load-balancer-api-internal: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 5.082246ms
      message: 'load-balancer-api-internal: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 7.84015ms
      message: 'load-balancer-api-internal: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 5.931742ms
      message: 'load-balancer-api-internal: tcp connection to a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 6.464865ms
      message: 'load-balancer-api-internal: resolved host name a24bbef0bf82249e198abe5ff37117d5-c0175a4a5fc237a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:15:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-130-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "31526"
    uid: 2e12efac-df67-4a6b-8cad-9c7ed10f45df
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:14:56Z"
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02842ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:21:56Z"
    - latency: 931.276µs
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:20:56Z"
    - latency: 873.902µs
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 1.230835ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 817.44µs
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 1.312491ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 883.75µs
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 1.437571ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:14:56Z"
    - latency: 963.212µs
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:13:56Z"
    - latency: 1.40781ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-142-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "31528"
    uid: 84bcbdeb-60f4-493d-9dcc-07530b4e186e
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:14:56Z"
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.137395ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:21:56Z"
    - latency: 2.344799ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:20:56Z"
    - latency: 2.706958ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 2.349055ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 2.210159ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 2.486689ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 2.624813ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 2.416708ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:14:56Z"
    - latency: 2.305965ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:13:56Z"
    - latency: 2.177043ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-142-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "31527"
    uid: 89d53318-a45f-4a7e-834b-113afa635e32
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:14:56Z"
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.723053ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:21:56Z"
    - latency: 2.408468ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:20:56Z"
    - latency: 2.014297ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 2.462027ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 2.376954ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 2.41613ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 2.104398ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 2.337742ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:14:56Z"
    - latency: 2.654028ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:13:56Z"
    - latency: 2.172386ms
      message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-07T16:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-133.ec2.internal
      uid: 05f4e5c0-5914-418f-b565-d55002d78d19
    resourceVersion: "29691"
    uid: 40717ea3-78eb-4c05-bdf7-95f64d184446
  spec:
    sourcePod: network-check-source-dbd9cf844-bztmm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-07T16:13:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 797.601µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 1.762131ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:19:56Z"
    - latency: 1.260203ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 1.720466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:18:56Z"
    - latency: 879.385µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 1.722034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:17:56Z"
    - latency: 871.346µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 2.082827ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:16:56Z"
    - latency: 1.141387ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-07T16:15:56Z"
    - latency: 1.656687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-07T16:15:56Z"
kind: List
metadata:
  resourceVersion: ""