interLink provider documentation #1214
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Diego Ciangottini <diego.ciangottini@pg.infn.it>
helayoty
reviewed
May 7, 2024
helayoty
requested changes
May 7, 2024
InterLink guide link fixed
|
Done, sorry about that! |
dciangot
added a commit
to dciangot/virtual-kubelet
that referenced
this pull request
May 13, 2024
Fixing interLink link in the website, introduced by virtual-kubelet#1214
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, this is to propose to include interLink in the list of providers.
We presented it at the last CNCF AI Day in Paris and then in the Research end user group, where I got the suggestion to show it as a provider here, although it is a project at early development stage.
For context, as mentioned in the content of the PR: "InterLink is a Virtual Kubelet provider that can manage container lifecycle through a well defined API specification, allowing for any resource provider to be integrated with a simple http server and a handful of methods.
In other words, this is an attempt to streamline the process of creating custom Virtual Kubelet providers, avoiding the need for any resource provider to implement its own version of a Kubelet workflow, which would require having some domain expertise in the Kubernetes internals."