reactive ui with client-node and kubectl proxy #445
Closed
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.
This update adds support for client-node javascript kubernetes client to show real-time view of the cluster resources. Whenever possible the js client is used, if it's not available, the extension will safely fallback to the
kubectl get
method for querying cluster state. The new system is labeled withk8s
prefix while the old system is calledkubectl get
orkubernetesTools
.The javascript client requires
kubectl proxy
process to be running to be authenticated to the server. The update extension watches and restarts thekubectl proxy
process as needed. Everything is reload when users click the "Refresh" buttons. Caching for namespaces is added. As much as possible all types used by the extension are moved to use client-node types, which are prefixed withk8s