apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "64711"
    uid: cd1aea8e-44ed-4cdb-b265-4193103d46e4
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:15:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 1.182819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 1.433301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 1.203608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 1.16659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:40Z"
    - latency: 1.266871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:40Z"
    - latency: 1.131048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:37:40Z"
    - latency: 1.133282ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:36:40Z"
    - latency: 774.282µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:35:40Z"
    - latency: 933.564µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "65373"
    uid: 0501c71b-699b-4c94-9a83-904ce8fcf7d4
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:14:40Z"
      message: 'load-balancer-api-external: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.749456ms
      message: 'load-balancer-api-external: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:40Z"
    - latency: 8.221991ms
      message: 'load-balancer-api-external: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:44:40Z"
    - latency: 2.983187ms
      message: 'load-balancer-api-external: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 9.021115ms
      message: 'load-balancer-api-external: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 3.980917ms
      message: 'load-balancer-api-external: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 8.173278ms
      message: 'load-balancer-api-external: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 4.9733ms
      message: 'load-balancer-api-external: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 8.854841ms
      message: 'load-balancer-api-external: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 3.647893ms
      message: 'load-balancer-api-external: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 8.062507ms
      message: 'load-balancer-api-external: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:40:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "65374"
    uid: f23ecabe-0662-4755-a25f-f7119b0155f0
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:14:40Z"
      message: 'load-balancer-api-internal: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.769981ms
      message: 'load-balancer-api-internal: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:40Z"
    - latency: 8.131356ms
      message: 'load-balancer-api-internal: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:44:40Z"
    - latency: 5.093298ms
      message: 'load-balancer-api-internal: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 8.990883ms
      message: 'load-balancer-api-internal: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 5.554769ms
      message: 'load-balancer-api-internal: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 8.108337ms
      message: 'load-balancer-api-internal: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 4.995792ms
      message: 'load-balancer-api-internal: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 8.820291ms
      message: 'load-balancer-api-internal: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 3.250088ms
      message: 'load-balancer-api-internal: tcp connection to a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 8.002457ms
      message: 'load-balancer-api-internal: resolved host name a46f5dbd823d243aba2521cfa080d3e7-7a5ddb840eec682f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:40:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-network-check-target-ip-10-0-129-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "64710"
    uid: 8b453335-54f5-4c8c-84a0-0f8f9252f45b
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:15:40Z"
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.156485ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 2.138871ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 2.271788ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 2.332777ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 2.275099ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:40Z"
    - latency: 2.331069ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:40Z"
    - latency: 2.3237ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:37:40Z"
    - latency: 2.64347ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:36:40Z"
    - latency: 2.019612ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:35:40Z"
    - latency: 2.237742ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-network-check-target-ip-10-0-137-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "64709"
    uid: 4451fdcb-999e-45b7-a8d6-fb04b2220f11
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:15:40Z"
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.038693ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 2.114882ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 2.217148ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 2.151715ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 2.068666ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:40Z"
    - latency: 2.28763ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:40Z"
    - latency: 2.290863ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:37:40Z"
    - latency: 2.405943ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:36:40Z"
    - latency: 2.39822ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:35:40Z"
    - latency: 2.27362ms
      message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-network-check-target-ip-10-0-139-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "64708"
    uid: c8c50dbf-ad25-43ca-9694-e5098d72246a
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:15:40Z"
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 672.584µs
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 832.46µs
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 933.771µs
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 1.441476ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 1.320077ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:40Z"
    - latency: 1.049622ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:40Z"
    - latency: 895.011µs
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:37:40Z"
    - latency: 893.503µs
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:36:40Z"
    - latency: 964.791µs
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:35:40Z"
    - latency: 1.576749ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-140-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-140.ec2.internal
      uid: 2c101313-0b5d-4e0c-8896-8e198a5513ac
    resourceVersion: "65372"
    uid: 58ac7d68-991e-49d3-84c3-c325ddc1f50b
  spec:
    sourcePod: network-check-source-6f8b768455-zgzs4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:14:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.379µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:40Z"
    - latency: 2.013957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:44:40Z"
    - latency: 1.00185ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 1.852656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:43:40Z"
    - latency: 849.503µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 1.666928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:42:40Z"
    - latency: 885.775µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 1.865301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:41:40Z"
    - latency: 851.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:40Z"
    - latency: 1.85257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:40:40Z"
kind: List
metadata:
  resourceVersion: ""