apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "52615"
    uid: 3b79fd97-7082-4766-9788-7c476b8d7fff
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:53:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 1.23984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 1.002728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 1.022773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:11:03Z"
    - latency: 1.185601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:10:03Z"
    - latency: 1.560937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:09:03Z"
    - latency: 1.568534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:08:03Z"
    - latency: 1.381999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:07:03Z"
    - latency: 1.164222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:03Z"
    - latency: 1.240164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "54636"
    uid: 81a481bb-619d-4256-ad56-e2cbe8d77241
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:52:03Z"
      message: 'load-balancer-api-external: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.475729ms
      message: 'load-balancer-api-external: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:16:03Z"
    - latency: 8.995744ms
      message: 'load-balancer-api-external: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:16:03Z"
    - latency: 6.326929ms
      message: 'load-balancer-api-external: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:15:03Z"
    - latency: 9.304928ms
      message: 'load-balancer-api-external: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:15:03Z"
    - latency: 4.789145ms
      message: 'load-balancer-api-external: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 9.474053ms
      message: 'load-balancer-api-external: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 5.72617ms
      message: 'load-balancer-api-external: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 8.703612ms
      message: 'load-balancer-api-external: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 5.590185ms
      message: 'load-balancer-api-external: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 8.799602ms
      message: 'load-balancer-api-external: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "54635"
    uid: 1e8b1353-71f9-4eb8-a626-cb40a64ded04
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:52:03Z"
      message: 'load-balancer-api-internal: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.433834ms
      message: 'load-balancer-api-internal: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:16:03Z"
    - latency: 9.119348ms
      message: 'load-balancer-api-internal: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:16:03Z"
    - latency: 6.368176ms
      message: 'load-balancer-api-internal: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:15:03Z"
    - latency: 9.24346ms
      message: 'load-balancer-api-internal: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:15:03Z"
    - latency: 4.866983ms
      message: 'load-balancer-api-internal: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 9.499988ms
      message: 'load-balancer-api-internal: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 5.463475ms
      message: 'load-balancer-api-internal: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 8.738483ms
      message: 'load-balancer-api-internal: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 5.600446ms
      message: 'load-balancer-api-internal: tcp connection to a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 8.721352ms
      message: 'load-balancer-api-internal: resolved host name a83813a18cd6a44ac8fc2911a873f843-ef3ca21485187ed6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-network-check-target-ip-10-0-134-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "52614"
    uid: 235fc298-6874-47f4-b264-db48adae9fe6
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:53:03Z"
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.606787ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 2.344338ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 2.298003ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 2.497009ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:11:03Z"
    - latency: 2.538403ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:10:03Z"
    - latency: 2.904275ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:09:03Z"
    - latency: 2.812893ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:08:03Z"
    - latency: 2.332263ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:07:03Z"
    - latency: 2.929352ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:03Z"
    - latency: 2.532693ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-network-check-target-ip-10-0-136-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "52612"
    uid: 6292e049-abbd-478b-adf7-03fb89f14831
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:53:03Z"
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.752µs
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 1.096789ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 909.083µs
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 1.462612ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:11:03Z"
    - latency: 981.992µs
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:10:03Z"
    - latency: 1.73364ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:09:03Z"
    - latency: 1.09293ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:08:03Z"
    - latency: 1.020243ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:07:03Z"
    - latency: 1.656074ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:03Z"
    - latency: 1.040683ms
      message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-network-check-target-ip-10-0-139-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "52613"
    uid: 713b6903-dd40-42fe-af54-4b609a9a0da0
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:53:03Z"
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.522142ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 2.795512ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 2.556225ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 2.468455ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:11:03Z"
    - latency: 2.104653ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:10:03Z"
    - latency: 2.666867ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:09:03Z"
    - latency: 2.604931ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:08:03Z"
    - latency: 2.707157ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:07:03Z"
    - latency: 2.134623ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:03Z"
    - latency: 2.572833ms
      message: 'network-check-target-ip-10-0-139-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-61.ec2.internal
      uid: cbc2cc46-50d8-4183-871b-7ae0866bfa76
    resourceVersion: "54634"
    uid: aaa8c89f-e368-4184-b5ef-e5db4134a70d
  spec:
    sourcePod: network-check-source-685456655f-pxwpp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:52:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156678ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:16:03Z"
    - latency: 1.935106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:16:03Z"
    - latency: 1.091833ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:15:03Z"
    - latency: 1.861746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:15:03Z"
    - latency: 959.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 2.349502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:14:03Z"
    - latency: 1.040303ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 1.776244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:13:03Z"
    - latency: 851.325µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:12:03Z"
    - latency: 1.820995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:12:03Z"
kind: List
metadata:
  resourceVersion: ""