apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "30245"
    uid: bde6b38f-a313-4d9c-932b-b947c36a83bb
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:27:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:34:27Z"
    - latency: 1.187694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:27Z"
    - latency: 1.133093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 1.119753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 1.071048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 1.261064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 1.1329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 1.492678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:27:27Z"
    - latency: 813.244µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:26:27Z"
    - latency: 1.69527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "28206"
    uid: e23f114b-058f-4161-8427-1f7737220a27
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:26:27Z"
      message: 'load-balancer-api-external: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.641683ms
      message: 'load-balancer-api-external: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 12.73874ms
      message: 'load-balancer-api-external: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 6.304474ms
      message: 'load-balancer-api-external: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 11.217308ms
      message: 'load-balancer-api-external: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 6.042859ms
      message: 'load-balancer-api-external: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 11.048086ms
      message: 'load-balancer-api-external: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 5.726589ms
      message: 'load-balancer-api-external: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 11.530107ms
      message: 'load-balancer-api-external: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 5.363679ms
      message: 'load-balancer-api-external: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 10.555443ms
      message: 'load-balancer-api-external: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "28207"
    uid: d5e16971-4472-4798-8924-598c0bb44b87
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:26:27Z"
      message: 'load-balancer-api-internal: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.953283ms
      message: 'load-balancer-api-internal: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 12.76941ms
      message: 'load-balancer-api-internal: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 5.811071ms
      message: 'load-balancer-api-internal: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 11.206446ms
      message: 'load-balancer-api-internal: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 6.050839ms
      message: 'load-balancer-api-internal: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 11.010357ms
      message: 'load-balancer-api-internal: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 5.658483ms
      message: 'load-balancer-api-internal: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 11.578785ms
      message: 'load-balancer-api-internal: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 5.362328ms
      message: 'load-balancer-api-internal: tcp connection to a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 10.461611ms
      message: 'load-balancer-api-internal: resolved host name a7a868c15ba5d4fa89831dd6a7049851-c92ece85d181fcc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-129-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "30242"
    uid: 393756ec-fd3f-4ff6-9593-13b6e50d3398
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:27:27Z"
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009596ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:34:27Z"
    - latency: 823.786µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:27Z"
    - latency: 1.287446ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 815.377µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 808.963µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 1.03008ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 1.316464ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 2.245295ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:27:27Z"
    - latency: 856.208µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:26:27Z"
    - latency: 1.116689ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-130-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "30243"
    uid: f640e493-fdcf-4f85-a84d-e0642e2b2d67
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:27:27Z"
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.167033ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:34:27Z"
    - latency: 2.084212ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:27Z"
    - latency: 2.035697ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 2.005048ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 1.807554ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 2.14556ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 2.122725ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 2.949987ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:27:27Z"
    - latency: 2.161581ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:26:27Z"
    - latency: 2.129093ms
      message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-132-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "30244"
    uid: 0744683b-3ed1-4f88-8f3d-1c926d5e483d
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:27:27Z"
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.102825ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:34:27Z"
    - latency: 2.108673ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:27Z"
    - latency: 1.84161ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 1.785103ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 2.151101ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 2.075583ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 2.177048ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 2.691784ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:27:27Z"
    - latency: 1.909558ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:26:27Z"
    - latency: 1.887809ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: 83e420a8-8453-4084-a4cc-102ea08e67ed
    resourceVersion: "28205"
    uid: b542583c-81f3-476d-9282-b7774228ebe3
  spec:
    sourcePod: network-check-source-dbd9cf844-pjtxf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:26:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.926µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 1.930976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:32:27Z"
    - latency: 967.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 1.826784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:31:27Z"
    - latency: 846.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 2.051397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:30:27Z"
    - latency: 1.17681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 1.726105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:29:27Z"
    - latency: 871.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:28:27Z"
    - latency: 1.792593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:28:27Z"
kind: List
metadata:
  resourceVersion: ""