apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "44060"
    uid: bf0d7cb8-7b54-4053-b2d6-327211fe6150
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:15:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.068538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 1.215359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 953.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 1.035694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:33:11Z"
    - latency: 839.207µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:32:11Z"
    - latency: 866.283µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:31:11Z"
    - latency: 1.131256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:30:11Z"
    - latency: 1.349655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:29:11Z"
    - latency: 1.54865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:28:11Z"
    - latency: 854.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:27:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "45818"
    uid: 9835f805-7c7b-4827-9a22-fd64b0ae6168
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:14:11Z"
      message: 'load-balancer-api-external: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.475338ms
      message: 'load-balancer-api-external: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:38:11Z"
    - latency: 8.250372ms
      message: 'load-balancer-api-external: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:38:11Z"
    - latency: 5.474731ms
      message: 'load-balancer-api-external: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:37:11Z"
    - latency: 7.172565ms
      message: 'load-balancer-api-external: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:37:11Z"
    - latency: 5.603061ms
      message: 'load-balancer-api-external: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 10.957553ms
      message: 'load-balancer-api-external: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 4.812539ms
      message: 'load-balancer-api-external: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 8.428464ms
      message: 'load-balancer-api-external: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 2.834748ms
      message: 'load-balancer-api-external: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 11.041841ms
      message: 'load-balancer-api-external: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:34:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "45819"
    uid: 9b340379-10c3-4007-a4d8-f03eae62368f
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:14:11Z"
      message: 'load-balancer-api-internal: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.367915ms
      message: 'load-balancer-api-internal: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:38:11Z"
    - latency: 8.285994ms
      message: 'load-balancer-api-internal: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:38:11Z"
    - latency: 5.478021ms
      message: 'load-balancer-api-internal: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:37:11Z"
    - latency: 7.10793ms
      message: 'load-balancer-api-internal: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:37:11Z"
    - latency: 5.270895ms
      message: 'load-balancer-api-internal: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 11.087801ms
      message: 'load-balancer-api-internal: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 6.89683ms
      message: 'load-balancer-api-internal: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 8.458998ms
      message: 'load-balancer-api-internal: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 3.528865ms
      message: 'load-balancer-api-internal: tcp connection to a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 11.0719ms
      message: 'load-balancer-api-internal: resolved host name a56938d968c7c4c6593bea4c42705c11-a76a371f9174f139.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:34:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-network-check-target-ip-10-0-131-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "44057"
    uid: fe74a07f-83e8-464d-8263-f6f52b4ba051
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:15:11Z"
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.922µs
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 884.23µs
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 1.312064ms
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 885.731µs
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:33:11Z"
    - latency: 1.539942ms
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:32:11Z"
    - latency: 991.447µs
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:31:11Z"
    - latency: 886.506µs
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:30:11Z"
    - latency: 1.171748ms
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:29:11Z"
    - latency: 1.090509ms
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:28:11Z"
    - latency: 917.978µs
      message: 'network-check-target-ip-10-0-131-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:27:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-network-check-target-ip-10-0-134-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "44059"
    uid: eb8ef37c-de19-4201-bf11-88acdb3cb190
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:15:11Z"
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.475587ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 2.187764ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 2.114572ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 2.178965ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:33:11Z"
    - latency: 2.195252ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:32:11Z"
    - latency: 2.239367ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:31:11Z"
    - latency: 2.204538ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:30:11Z"
    - latency: 2.134367ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:29:11Z"
    - latency: 2.178723ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:28:11Z"
    - latency: 2.284945ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:27:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-network-check-target-ip-10-0-137-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "44058"
    uid: b7c815c4-0429-4917-a49f-5713b1a02569
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:15:11Z"
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.962905ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 1.907043ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 1.962495ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 1.911894ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:33:11Z"
    - latency: 2.1496ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:32:11Z"
    - latency: 1.701911ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:31:11Z"
    - latency: 1.835972ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:30:11Z"
    - latency: 1.87021ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:29:11Z"
    - latency: 1.920749ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:28:11Z"
    - latency: 1.838045ms
      message: 'network-check-target-ip-10-0-137-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:27:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:08:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-50-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-50.ec2.internal
      uid: 3d7a5b7f-2e0b-40d0-babb-22caa82355d4
    resourceVersion: "45817"
    uid: 7c876478-dc48-4d67-b1e5-d67e7f2e6e81
  spec:
    sourcePod: network-check-source-56d84b9f44-7fks2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:14:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.589µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:38:11Z"
    - latency: 1.711124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:38:11Z"
    - latency: 867.848µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:37:11Z"
    - latency: 1.694751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:37:11Z"
    - latency: 858.723µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 3.74853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:36:11Z"
    - latency: 1.074907ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 1.746173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:35:11Z"
    - latency: 829.124µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:34:11Z"
    - latency: 1.742216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:34:11Z"
kind: List
metadata:
  resourceVersion: ""