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

Add information to README for csi-driver-nfs #3

Closed
saad-ali opened this issue Feb 15, 2019 · 5 comments · Fixed by #27
Closed

Add information to README for csi-driver-nfs #3

saad-ali opened this issue Feb 15, 2019 · 5 comments · Fixed by #27
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@saad-ali
Copy link
Member

Add the follow information:

  • What version of CSI does this driver support
  • What is the status of this driver (alpha).
  • Which of the following (optional) features does this driver support:
    • dynamic provisioning
    • online resize or offline resize
    • block
    • snapshot
  • Which AccessModes does this driver support?

/assign @prateekpandey14

@k8s-ci-robot
Copy link
Contributor

@saad-ali: GitHub didn't allow me to assign the following users: prateekpandey14.

Note that only kubernetes-csi members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Add the follow information:

  • What version of CSI does this driver support
  • What is the status of this driver (alpha).
  • Which of the following (optional) features does this driver support:
    • dynamic provisioning
    • online resize or offline resize
    • block
    • snapshot
  • Which AccessModes does this driver support?

/assign @prateekpandey14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@msau42 msau42 added this to To do in Common drivers Feb 16, 2019
pohly pushed a commit to pohly/csi-driver-nfs that referenced this issue Feb 20, 2019
mathu97 pushed a commit to mathu97/csi-driver-nfs that referenced this issue Mar 22, 2019
# This is the 1st commit message:

setup travis running e2e tests on the nfs driver

# The commit message kubernetes-csi#2 will be skipped:

# remove release-tools

# The commit message kubernetes-csi#3 will be skipped:

# test travis with no makefile in config

# The commit message kubernetes-csi#4 will be skipped:

# change path

# The commit message kubernetes-csi#5 will be skipped:

# adding e2e test to travis ci

# The commit message kubernetes-csi#6 will be skipped:

# add travis build status on README

# The commit message kubernetes-csi#7 will be skipped:

# fix travis script

# The commit message kubernetes-csi#8 will be skipped:

# use local-up-cluster instead of dind for travis CI
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 16, 2019
@msau42
Copy link
Collaborator

msau42 commented Jun 7, 2019

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 7, 2019
@msau42
Copy link
Collaborator

msau42 commented Jun 7, 2019

@mathu97 could you help update the readme?

@mathu97
Copy link
Contributor

mathu97 commented Jun 7, 2019

@msau42 yes, will get on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Development

Successfully merging a pull request may close this issue.

5 participants