apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60767"
    uid: c50ff5d7-026c-4c89-84e5-b5194c8e6a89
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:04:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.439µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 1.155394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 796.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 1.39498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 1.202903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 981.272µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:34:05Z"
    - latency: 1.056937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:33:05Z"
    - latency: 1.540736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:32:05Z"
    - latency: 1.650673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:31:05Z"
    - latency: 961.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:30:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60769"
    uid: 7c29dc46-3d15-463a-ad61-7e74efb0938a
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:03:05Z"
      message: 'load-balancer-api-external: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.92076ms
      message: 'load-balancer-api-external: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 7.829149ms
      message: 'load-balancer-api-external: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 7.161914ms
      message: 'load-balancer-api-external: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 8.249515ms
      message: 'load-balancer-api-external: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 4.396822ms
      message: 'load-balancer-api-external: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 8.152776ms
      message: 'load-balancer-api-external: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 3.732533ms
      message: 'load-balancer-api-external: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 6.439341ms
      message: 'load-balancer-api-external: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 4.333527ms
      message: 'load-balancer-api-external: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 7.030802ms
      message: 'load-balancer-api-external: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:35:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60768"
    uid: 5ca91323-0060-4674-8f4c-5c1463d15a6e
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:03:05Z"
      message: 'load-balancer-api-internal: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.169153ms
      message: 'load-balancer-api-internal: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 7.809743ms
      message: 'load-balancer-api-internal: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 4.361963ms
      message: 'load-balancer-api-internal: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 8.310795ms
      message: 'load-balancer-api-internal: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 4.429518ms
      message: 'load-balancer-api-internal: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 8.102399ms
      message: 'load-balancer-api-internal: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 3.71932ms
      message: 'load-balancer-api-internal: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 6.472235ms
      message: 'load-balancer-api-internal: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 4.57559ms
      message: 'load-balancer-api-internal: tcp connection to ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 6.947168ms
      message: 'load-balancer-api-internal: resolved host name ad41ba3f1ae9345f1afc31a8dfc37d73-b05a11b245d7dc9b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:35:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-network-check-target-ip-10-0-131-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60762"
    uid: f6ad9d0e-9dbb-4bc4-944a-77d9e04dc1c2
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:04:05Z"
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 742.515µs
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 931.686µs
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 1.134273ms
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 1.478334ms
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 1.058956ms
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 994.694µs
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:34:05Z"
    - latency: 902.295µs
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:33:05Z"
    - latency: 1.251991ms
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:32:05Z"
    - latency: 866.977µs
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:31:05Z"
    - latency: 856.593µs
      message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:30:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-network-check-target-ip-10-0-132-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60766"
    uid: 2c5a256f-745b-413f-8b1f-53a19b2fb4eb
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:04:05Z"
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.488503ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 2.196858ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 2.572577ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 2.505674ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 2.455109ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 2.46579ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:34:05Z"
    - latency: 2.314066ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:33:05Z"
    - latency: 2.212146ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:32:05Z"
    - latency: 2.331422ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:31:05Z"
    - latency: 2.092345ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:30:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-network-check-target-ip-10-0-143-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60763"
    uid: c8f27f54-9183-425e-a1b4-1d977f526dec
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:04:05Z"
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.473079ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 2.329452ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 2.111276ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 3.035515ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 2.309863ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 2.425185ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:34:05Z"
    - latency: 3.222934ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:33:05Z"
    - latency: 2.457347ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:32:05Z"
    - latency: 2.236679ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:31:05Z"
    - latency: 2.196914ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:30:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-27-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-27.ec2.internal
      uid: 33c40b41-1951-4c77-9660-143383561d68
    resourceVersion: "60765"
    uid: dc97c074-bc5d-43ff-8df2-e98ab3a6282a
  spec:
    sourcePod: network-check-source-869dcfcdcd-j8zkl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:03:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 677.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 2.549987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:39:05Z"
    - latency: 833.21µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 1.750578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:38:05Z"
    - latency: 941.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 2.074608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:37:05Z"
    - latency: 1.124357ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 1.769798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:36:05Z"
    - latency: 980.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:35:05Z"
    - latency: 1.710433ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:35:05Z"
kind: List
metadata:
  resourceVersion: ""