question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Distributing kui plugins via krew

See original GitHub issue

Describe the topic Distributing kui plugins via krew.

This topic was discussed twice during SIG-CLI meetings with a small demo on Oct 9.

Kui plugins should be lightweight in that not every UI plugin installs its own electron/chromium dependencies. For that they need some dependency management on the kui side. The idea is to have a helper (?kask?) which takes care of providing runtime dependencies for UI plugins. The plugins themselves can then be rather slim and install just the bundle of node_modules and program logic. (please correct me, if I got something wrong here).

Kui developers raised the idea that those plugins could be distributed via krew. So let’s talk about what are the requirements that kui has for plugin management. This will help krew understand what would be needed to support this use-case. Also, there may be some easy steps to be taken by krew to unblock further development on kui side.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:24 (14 by maintainers)

github_iconTop GitHub Comments

1reaction
starpitcommented, Oct 22, 2019

kask itself would be under the management of krew. the chain-installed kui-base would not be under krew’s management, but rather managed by kask.

it is a trade-off we can explore. i want to keep the discussion open, for now, because there are foreseeable (but possibly ignoreable) issues with having one chromium per plugin; e.g. every plugin launch would add a separate icon to the macOS dock

0reactions
k8s-ci-robotcommented, May 23, 2021

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Distributing kui plugins via krew · Issue #2962 · kubernetes-sigs/kui ...
Kui plugins should be lightweight in that not every UI plugin installs its own electron/chromium dependencies. For that they need some dependency management...
Read more >
Distributing plugins on Krew - Kubernetes
Distributing the plugin executable using an OS package manager, like Homebrew (macOS), apt/yum (Linux), or Chocolatey (Windows); Distributing the plugin ...
Read more >
Extend kubectl with plugins - Kubernetes
If you have developed a plugin for others to use, you should consider how you package it, distribute it and deliver updates to...
Read more >
Kubernetes Plugins, Tools, Extensions and Projects - Nubenetes
With Permission Manager, you can create users, assign namespaces/permissions, and distribute Kubeconfig YAML files via a nice & easy web UI.
Read more >
@kui-shell/plugin-openshift NPM | npm.io
@kui-shell/plugin-openshift v1.0.17 · Kubernetes UI Plugin for Kui · Prebuilt Images · Code and Contribute · Edit-debug Loop · Building a Distribution.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found