gitRepo volume k3s not working

[andresetevejob]

Version:

K3s arguments:

Describe the bug

Pod is never created when, i use gitRepo for volume
To Reproduce

Create a pod with this yaml :
apiVersion: v1
kind: Pod
metadata:
name: gitrepo-volume-pod
spec:
containers:

• image: nginx:alpine
  name: web-server
  volumeMounts:
  • name: html
    mountPath: /usr/share/nginx/html
    readOnly: true
    ports:
  • containerPort: 80
    protocol: TCP
    volumes:
• name: html
  gitRepo:
  repository: https://github.com/andresetevejob/smsmonitoringweb.
  revision: master
  directory: .

Expected behavior

Pod should be created,a the git repository should be clone
Actual behavior

Pod is never created
Additional context / logs

Events:
Type Reason Age From Message

---

Normal Scheduled default-scheduler Successfully assigned default/gitrepo-volume-pod to k3s
Warning FailedMount 10s kubelet, k3s Unable to attach or mount volumes: unmounted volumes=[htmls], unattached volumes=[default-token-spbmg htmls]: failed to get Plugin from volumeSpec for volume "htmls" err=no volume plugin matched

[brandond]

From the README:

k3s is intended to be a fully compliant Kubernetes distribution with the following changes:

* Removed most in-tree plugins (cloud providers and storage plugins) which can be replaced with out of tree addons.

The gitRepo volume type has been deprecated for several years, so I'm not surprised it's not included:
kubernetes/kubernetes#63445

[davidnuzik]

Please do not exclude version information and args used to install k3s when filing issues.

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.