external-provisioner | Sidecar container that watches Kubernetes | Storage library

by kubernetes-csi Go Version: v3.5.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | external-provisioner Summary

external-provisioner is a Go library typically used in Storage applications. external-provisioner has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The external-provisioner is an external controller that monitors PersistentVolumeClaim objects created by user and creates/deletes volumes for them. Full design can be found at Kubernetes proposal at container-storage-interface.md.

Support

Quality

Security

License

Reuse

Support

external-provisioner has a low active ecosystem.

It has 269 star(s) with 287 fork(s). There are 31 watchers for this library.

It had no major release in the last 12 months.

There are 15 open issues and 206 have been closed. On average issues are closed in 273 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of external-provisioner is v3.5.0

Quality

external-provisioner has no bugs reported.

Security

external-provisioner has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

external-provisioner is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

external-provisioner releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of external-provisioner

Get all kandi verified functions for this library.

external-provisioner Key Features

No Key Features are available at this moment for external-provisioner.

external-provisioner Examples and Code Snippets

No Code Snippets are available at this moment for external-provisioner.

Community Discussions

Trending Discussions on external-provisioner

Kubernetes nfs provider selfLink was empty

kubectl create secret generic InternalError PermissionDenied

Kubernetes: What is the best practice for create dynamic local volume to auto assign PVs for PVCs?

QUESTION

Kubernetes nfs provider selfLink was empty

Asked 2020-Dec-21 at 14:26

Yesterday I created a new kubernetes cluster (v1.20.1, on prem) and I wanted to add NFS provisioning. The only NFS provisioner available (and still maintained) seems to be https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner.

It does say to use your own provisioner and the default (quay.io/external_storage/nfs-client-provisioner:latest) is two years old, but I don't have my own provisioner.

When I follow the deployment guide without the helm chart and check the nfs-client-provisioner log I see the following:

...

ANSWER

Answered 2020-Dec-21 at 09:52

You are seeing this error beacause of this: KEP-1164: Deprecate and Remove SelfLink

Quote from mentioned KEP:

In v1.16, we will deprecate the SelfLink field in both ObjectMeta and ListMeta objects by: documenting in field definition that it is deprecated and is going to be removed adding a release-note about field deprecation We will also introduce a feature gate to allow disabling setting SelfLink fields and opaque the logic setting it behind this feature gate.

In v1.20 (12 months and 4 release from v1.16) we will switch off the feature gate which will automatically disable setting SelfLinks. However it will still be possible to revert the behavior by changing value of a feature gate.

In v1.21, we will get rid of the whole code propagating those fields and fields themselves. In the meantime, we will go over places referencing that field (see below) and get rid of those too.

As you see, you can enable it back with featureGate: RemoveSelfLink=false although its not recommented and SelfLink will be permamently removed in v1.21

Also check this issue on github: Using Kubernetes v1.20.0, getting "unexpected error getting claim reference: selfLink was empty, can't make reference

Source https://stackoverflow.com/questions/65376314

QUESTION

kubectl create secret generic InternalError PermissionDenied

Asked 2020-Nov-17 at 18:22

I've configured access to my K8s cluster, set up all needed pods &services, created secrets with YAML files, but this simple command:

...

ANSWER

Answered 2020-Nov-17 at 18:22

I found the solution: I had to set the role kms.keys.encrypterDecrypter to the service account which is used to control Kubernetes cluster in the settings of Yandex.Cloud project catalog.

Source https://stackoverflow.com/questions/64846525

QUESTION

Kubernetes: What is the best practice for create dynamic local volume to auto assign PVs for PVCs?

Asked 2020-Jul-05 at 11:29

Recently, I installed the k8s via kubeadm init on my CentOS7 clusters. Unfortunately, I suffered a lots of problems. The biggest problem is "How to create a dynamic local storage/volume for automatically assign PVs for PVCs?"

Q: Why local storage not cloud storage service?

A: This is a limitation of new lab of my university.

Problem description:

The k8s(v1.18.0) did not create a default storage class for me after the installing process successfully. I not sure about that whether the situation normally. However, when I install my first application, JupyterHub, on k8s, I got error from it because it could found a suitable PV to fit a PVC hub-db-dir. And then I attempt to manually a local storage class and a PV such below:

local-storage.yaml

...

ANSWER

Answered 2020-Jul-05 at 11:29

High level steps to achieve dynamic PV creation using local-storage StorageClass

From the docs here on how to manage local volumes in your Kubernetes cluster.

Create a directory for provisioner discovering
Prepare and set up local volumes in discovery directory

Next from the docs here

Create a StorageClass
Create local persistent volumes

Source https://stackoverflow.com/questions/62739026

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install external-provisioner

You can download it from GitHub.

Support

When Topology feature is enabled and the driver specifies VOLUME_ACCESSIBILITY_CONSTRAINTS in its plugin capabilities, external-provisioner prepares CreateVolumeRequest.AccessibilityRequirements while calling Controller.CreateVolume. The driver has to consider these topology constraints while creating the volume. Below table shows how these AccessibilityRequirements are prepared:.

Find more information at: