Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitRepo volume k3s not working #1654

Closed
andresetevejob opened this issue Apr 19, 2020 · 3 comments
Closed

gitRepo volume k3s not working #1654

andresetevejob opened this issue Apr 19, 2020 · 3 comments

Comments

@andresetevejob
Copy link

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:

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
Copy link
Member

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
Copy link
Contributor

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

@stale
Copy link

stale bot commented Jul 31, 2021

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.

@stale stale bot added the status/stale label Jul 31, 2021
@stale stale bot closed this as completed Aug 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants