Ricardo Sanchez

Results 19 comments of Ricardo Sanchez

Root cause is that `longhorn-driver-deployer` is not able to communicate with `longhorn-manager` when checking the MointPropagation option. The log error printed by the pod is misleading. This error in the...

Linkerd iptables forwarding rules makes that all received traffic by the meshed containers appears to come from localhost. There is a linkerd open issue (https://github.com/linkerd/linkerd2/issues/4713) for changing linkerd's default behavior...

## Using Kustomize with Helm to automatically modify POD_IP Helm provides the possibility of manipulate, configure, and/or validate rendered manifests before they are installed by Helm: [`--post-rendering` option](https://helm.sh/docs/topics/advanced/#post-rendering). This enables...

Longhorn still does not completely start when patching the POD_IP environment using the previously described procedure (helm + post-rendering with kustomize) and including the corresponding helm chart parameter (`annotations` in...

Longhorn provides a [`environment_check.sh` script](https://github.com/longhorn/longhorn/blob/master/scripts/environment_check.sh) that makes the mount propagation check validation. Executing the script in my environment shows that the mount propagation is enabled in my cluster: ```shell daemonset.apps/longhorn-environment-check...

Opened a bug in longhorn repository (https://github.com/longhorn/longhorn/issues/3809)

Close by mistake. As part of PR #48, `longhorn-manager` and `longhorn-ui` have been meshed with linkerd after Longhorn has been successfully deployed. 1) `longhorn-manager` POD_IP environment variable is changed 2)...

## Procedure for obtaining raw metrics exposed by K3S. The procedure described here https://github.com/SUSE/doc-caasp/issues/166#issuecomment-476191064 can be used to manually query https metrics endpoints. Most recent versions of Kubernetes are moving...

## Possible solution. Enabling only monitoring of kubelet endpoints `/metrics`, `/metrics/cadvisor` and `/metrics/probes` available on TCP port 10250, so all metrics can be collected. This is the same solution [rancher...

Final solution setting job label to "kubelet" for all metrics scrapped for k3s components through kubelet port. This way only a few dashboards need to be changed. (kube-proxy, kube-controller-manager and...