virtual-kubelet | Virtual Kubelet is an open source Kubernetes kubelet

by virtual-kubelet Go Version: v1.9.0 License: Apache-2.0

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

kandi X-RAY | virtual-kubelet Summary

virtual-kubelet is a Go library. virtual-kubelet has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Virtual Kubelet is an open source Kubernetes kubelet implementation that masquerades as a kubelet for the purposes of connecting Kubernetes to other APIs. This allows the nodes to be backed by other services like ACI, AWS Fargate, IoT Edge, Tensile Kube etc. The primary scenario for VK is enabling the extension of the Kubernetes API into serverless container platforms like ACI and Fargate, though we are open to others. However, it should be noted that VK is explicitly not intended to be an alternative to Kubernetes federation. Virtual Kubelet features a pluggable architecture and direct use of Kubernetes primitives, making it much easier to build on. We invite the Kubernetes ecosystem to join us in empowering developers to build upon our base. Join our slack channel named, virtual-kubelet, within the Kubernetes slack group. The best description is "Kubernetes API on top, programmable back.".

Support

Quality

Security

License

Reuse

Support

virtual-kubelet has a medium active ecosystem.

It has 3840 star(s) with 588 fork(s). There are 105 watchers for this library.

It had no major release in the last 12 months.

There are 46 open issues and 316 have been closed. On average issues are closed in 491 days. There are 12 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of virtual-kubelet is v1.9.0

Quality

virtual-kubelet has 0 bugs and 0 code smells.

Security

virtual-kubelet has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

virtual-kubelet code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

virtual-kubelet 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

virtual-kubelet releases are available to install and integrate.

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

It has 11096 lines of code, 524 functions and 120 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

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 virtual-kubelet

Get all kandi verified functions for this library.

virtual-kubelet Key Features

No Key Features are available at this moment for virtual-kubelet.

virtual-kubelet Examples and Code Snippets

No Code Snippets are available at this moment for virtual-kubelet.

Community Discussions

Trending Discussions on virtual-kubelet

dask kubernetes aks (azure) virtual nodes

az aks install-connector fails with "--name unknown parameter"

QUESTION

dask kubernetes aks (azure) virtual nodes

Asked 2020-Jul-22 at 14:29

Using the code bellow it is possible to create a dask kubernetes cluster in azure aks.

It uses a remote scheduler (dask.config.set({"kubernetes.scheduler-service-type": "LoadBalancer"})) and works perfectly.

To use virtual nodes, uncomment the line extra_pod_config=virtual_config (which follows this official example).

It doesn't work, with the following error:

ACI does not support providing args without specifying the command. Please supply both command and args to the pod spec.

This is tied to passing containers: args: [dask-scheduler]

Which containers: command: should I supply to fix this issue?

Thank you

...

ANSWER

Answered 2020-Jul-22 at 14:29

the reason comes from this virtual kubelet protection: in the pod configuration, dask uses args to start a scheduler or worker, but no command is supplied.

So I explicitly added the entrypoint command command_entrypoint_explicit and it works: pods are created sucessfully.

Second problem: network names resolution. workers fail to connect to the scheduler by network name: tcp://{name}.{namespace}:{port}

Although tcp://{name}.{namespace}.svc.cluster.local:{port} works. I edited this in dask_kubernetes.core.Scheduler.start and it works.

Another option is the virtual_config bellow. Code bellow is a complete solution.

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

QUESTION

az aks install-connector fails with "--name unknown parameter"

Asked 2020-Feb-05 at 04:32

I am trying to install a test Kubernetes cluster. I the latest version of Azure CLI on my computer along with the latest Helm. When I run the command:

...

ANSWER

Answered 2020-Feb-05 at 01:55

It caused by helm 3. Actually the CLI command az aks install-connector will use helm 3 to install the chart that shows in it. But the helm 3 does not have the flag --name, see the helm 3 commands. So it will cause the error:

Error: unknown flag: --name

You can see the flag --name in helm 2 commands.

The solution is that you can skip the CLI command and use the helm 3 directly to install the chart in the AKS cluster. And you can find the chart in the parameter --chart-url of the CLI command here. Or use the helm 2 instead of helm 3.

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

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