apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "19054"
    uid: f103de37-b14c-4f06-8199-dff1366fafdf
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:57:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.188445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 1.037565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:03:48Z"
    - latency: 1.068943ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:02:48Z"
    - latency: 916.382µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:01:48Z"
    - latency: 2.100041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:00:48Z"
    - latency: 1.003759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:59:48Z"
    - latency: 1.088959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:58:48Z"
    - latency: 977.548µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:57:48Z"
    - latency: 826.819µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:56:48Z"
    - latency: 1.224136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:55:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "21090"
    uid: 4c629143-a943-4d03-b0de-ff3d7a7e4d73
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56:48Z"
      message: 'load-balancer-api-external: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.394725ms
      message: 'load-balancer-api-external: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:08:48Z"
    - latency: 12.968887ms
      message: 'load-balancer-api-external: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:08:48Z"
    - latency: 5.357362ms
      message: 'load-balancer-api-external: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:07:48Z"
    - latency: 8.281466ms
      message: 'load-balancer-api-external: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:07:48Z"
    - latency: 7.376372ms
      message: 'load-balancer-api-external: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:06:48Z"
    - latency: 15.762026ms
      message: 'load-balancer-api-external: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:06:48Z"
    - latency: 4.574055ms
      message: 'load-balancer-api-external: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:05:48Z"
    - latency: 14.230164ms
      message: 'load-balancer-api-external: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:05:48Z"
    - latency: 4.452908ms
      message: 'load-balancer-api-external: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 10.296979ms
      message: 'load-balancer-api-external: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:04:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "21091"
    uid: 62404c81-661a-469b-ad36-e22c9af1415f
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56:48Z"
      message: 'load-balancer-api-internal: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.366942ms
      message: 'load-balancer-api-internal: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:08:48Z"
    - latency: 12.929683ms
      message: 'load-balancer-api-internal: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:08:48Z"
    - latency: 4.593722ms
      message: 'load-balancer-api-internal: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:07:48Z"
    - latency: 8.440614ms
      message: 'load-balancer-api-internal: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:07:48Z"
    - latency: 8.729816ms
      message: 'load-balancer-api-internal: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:06:48Z"
    - latency: 15.649136ms
      message: 'load-balancer-api-internal: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:06:48Z"
    - latency: 4.52637ms
      message: 'load-balancer-api-internal: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:05:48Z"
    - latency: 14.284711ms
      message: 'load-balancer-api-internal: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:05:48Z"
    - latency: 4.414102ms
      message: 'load-balancer-api-internal: tcp connection to a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 10.336582ms
      message: 'load-balancer-api-internal: resolved host name a1909d1b404504546a4bc11fb8a24dca-ca5ffe30a19d8038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:04:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-network-check-target-ip-10-0-135-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "19052"
    uid: d87f7cd4-3bf1-40bc-9103-dfe91aefb341
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:57:48Z"
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.833368ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 1.816421ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:03:48Z"
    - latency: 1.769918ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:02:48Z"
    - latency: 1.852286ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:01:48Z"
    - latency: 2.304321ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:00:48Z"
    - latency: 1.955624ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:59:48Z"
    - latency: 1.751565ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:58:48Z"
    - latency: 2.371285ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:57:48Z"
    - latency: 1.74384ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:56:48Z"
    - latency: 1.801516ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:55:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-network-check-target-ip-10-0-137-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "19051"
    uid: ce987b3d-d862-496c-bafe-ee4e08758dcf
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:57:48Z"
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.251809ms
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 847.717µs
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:03:48Z"
    - latency: 835.479µs
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:02:48Z"
    - latency: 1.019217ms
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:01:48Z"
    - latency: 924.214µs
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:00:48Z"
    - latency: 820.52µs
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:59:48Z"
    - latency: 993.737µs
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:58:48Z"
    - latency: 1.346761ms
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:57:48Z"
    - latency: 865.317µs
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:56:48Z"
    - latency: 1.064916ms
      message: 'network-check-target-ip-10-0-137-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:55:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-network-check-target-ip-10-0-137-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "19053"
    uid: b915865a-9c48-49ce-b1dc-fcf62740522d
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:57:48Z"
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.271558ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 2.272059ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:03:48Z"
    - latency: 2.09196ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:02:48Z"
    - latency: 2.137751ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:01:48Z"
    - latency: 15.055151ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:00:48Z"
    - latency: 2.375733ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:59:48Z"
    - latency: 2.135664ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:58:48Z"
    - latency: 2.610809ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:57:48Z"
    - latency: 2.205401ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:56:48Z"
    - latency: 2.108959ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:55:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:50:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-113-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-113.ec2.internal
      uid: 7e804de7-e804-402c-853d-fda8a993e29b
    resourceVersion: "21089"
    uid: a96ab1fd-4ae9-4843-b3fa-29fb85a26f77
  spec:
    sourcePod: network-check-source-56499946bc-wr5r5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:56:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:08:48Z"
    - latency: 1.713083ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:08:48Z"
    - latency: 1.018807ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:07:48Z"
    - latency: 1.802541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:07:48Z"
    - latency: 1.07375ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:06:48Z"
    - latency: 1.73013ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:06:48Z"
    - latency: 833.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:05:48Z"
    - latency: 1.960608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:05:48Z"
    - latency: 1.096546ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:04:48Z"
    - latency: 1.744575ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:04:48Z"
kind: List
metadata:
  resourceVersion: ""