HostPath Mapper
This feature is an Enterprise feature. See our pricing plans or contact our sales team for more information.
Virtual cluster internal logging uses a separate component called the HostPath Mapper. This component matches virtual pod and container names to their real physical names.
If you don't configure host path mapping, log collectors such as Loki, ELK, and Fluentd incorrectly resolve logs for vCluster pods.
vCluster Open Source​
Enable the HostPath Mapper​
Set enabled: true
in the vCluster config to allow it to use the HostPath Mapper DaemonSet.
controlPlane:
hostPathMapper:
enabled: true
Deploy the HostPath Mapper DaemonSet​
After setting up the vCluster, deploy the HostPath Mapper component. Before you deploy the HostPath Mapper component, make sure the following requirements are met:
- Deploy the HostPath Mapper in the same namespace as the vCluster.
- Set the
.Values.vclusterReleaseName
field in the Helm chart to match the vCluster name.
For example, if the vCluster name is my-vcluster
and the namespace is my-namespace
, run the following command:
helm install vcluster-hpm vcluster-hpm \
--repo https://charts.loft.sh \
-n my-namespace \
--set VclusterReleaseName=my-vcluster
After deployment, the HostPath Mapper DaemonSet starts running on every node that hosts vCluster workloads.
vCluster Pro​
The Central HostPath Mapper enables the following in a virtual cluster:
- Container-based logging used by tools such as fluentd and Logstash.
- Pod-based logging used by Grafana Loki.
- Velero restic backups.
- KubeVirt workloads.
For more information about configuring vCluster and installing the Central HostPath Mapper, see Central HostPath Mapper in the platform documentation.