Comments (6)
hello there. thanks for sharing some great thoughts!
each top-level tab in kui should lock itself to a kubernetes context, but currently this only happens after a command execution, in that tab, to change context. it should be possible to add support for expressing the desire that this should happen onload, perhaps via a topmatter element.
markdown tabs currently do not have this capability. there also isn't a great way to add any kind of topmatter to a tab (we are using the pymdown/mkdocs syntax, which is pretty limiting in this respect)
one other thing we could do is add a bit of metadata support to kui's markdown code block implementation. right now, you can express things like
```shell
---
execute: now
---
```
i.e. kui does support adding a "topmatter" element to each code block (in this case, the execute: now
tells kui that you want it to execute the code block on the initial render, rather than when the user clicks to execute.
we could add context: xxx
support, perhaps? or maybe more generally, a suffix: --context west
, where kui will automatically add the given suffix to the command line execution?
🤔
from kui.
Thanks @starpit
So, if i was to approach this (without major customization), I would set up two top level tabs:
East
0. Set kube context
- Perform step
- Switch to West tab to perform step X
- Perform step
West
0. Set kube context
- Perform step
- Switch back to East tab to perform step Y
- Perform step
I'm not sure how auto-executing steps would help me, so, for now I think my best option is to generate markdown with the context embedded, eg skupper init --namespace west
thanks @starpit Any pointers for new kui users who want to create markdown notebooks, I'm currently using https://github.com/kui-shell/KuiClientTemplate but I dunno if that's the best option... Ideally I want the flow for skupper users to be:
- Install kui
- Run the skupper notebook
but is that what folks do? (I'm not finding any doc for that flow)
from kui.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from kui.
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
from kui.
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Reopen this issue with
/reopen
- Mark this issue as fresh with
/remove-lifecycle rotten
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
from kui.
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied- After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied- After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closedYou can:
- Reopen this issue with
/reopen
- Mark this issue as fresh with
/remove-lifecycle rotten
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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.
from kui.
Related Issues (20)
- Annotations tab shows up even for kubernetes resources with no annotations HOT 5
- clicking on a row of `helm ls` does `helm get` that gives an error
- On windows kubectl commands hang HOT 7
- How to Load Bash Profile in Mac HOT 5
- Mobile friendly homepage HOT 4
- Logs doesn't show up in v 13.1.1 HOT 3
- Error starting up pty Error: node-loader after brew install HOT 3
- How to deploy kui hosted client-server in a k8s server ? HOT 7
- Commands autocompletion is not working HOT 8
- Uncaught TypeError exception after kubectl kui if kui window is already open HOT 3
- Logs tab should track initContainers HOT 4
- Flow Tab missing HOT 4
- kubectl get --watch tables should eventually remove terminated resources HOT 4
- Update kubectl Logs tab to use xterm's search, rather than our home-grown HOT 6
- kubectl Logs Previous does not pay attention to current container selection HOT 4
- Save Feature or Folder for Markdown Files in Windows HOT 8
- `top` not working HOT 10
- 'kubectl get' does not work as expected for some resources HOT 5
- deployment -> pods uses incorrect label selector HOT 1
- Unable to access logs or terminal on Linux via WSL
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kui.