provide "describe" like in vscode

[adietish]

taken from #548 (comment)
CC @cloorc

"Describe" is provided in the context menu of resource tree items in vscode.

It prints detailed informations about a k8s resources.

[adietish]

"Find" (Ctrl+F) is already helpful to pinpoint informations that one is looking for. Maybe a tree based display of the sections (Metadata, Containers, Conditions, Volumes, etc.) could help even more. A shortcut could be to print the informations as yaml since the yaml editor provides breadcrumb navigation and folding.

@cloorc: thoughts?

[cloorc]

And further more, I will try to integrate helm command line tools too. That will enrich features as vscode plugin, which has been added with at least 5 more features from the ms official one.

[cloorc]

And further more, I will try to integrate helm command line ols too. That will enrich features as vscode plugin, which has been added with at least 5 more features from the ms official one.

"Find" (Ctrl+F) is already helpful to pinpoint informations that one is looking for. Maybe a tree based display of the sections (Metadata, Containers, Conditions, Volumes, etc.) could help even more. A shortcut could be to print the informations as yaml since the yaml editor provides breadcrumb navigation and folding.

@cloorc: thoughts?

I'm gonna to try from shortcut to experience this feature thanks.

[adietish]

@cloorc we added basic HELM support in our intellij-openshift-connector plugin: https://youtu.be/lvILs3fYJ2g

[cloorc]

Wonderful plugin, thanks for your excellent work. I'm going to try this.

[adietish]

jetbrains also allows to describe resources via the context menu:

The output is shown in an editor:

[cloorc]

Sorry, I can't even build it from vscode online in codespace. It said > /opt/java/11.0.14/Packages does not exist.

[cloorc]

Sorry, I can't even build it from vscode online in codespace. It said > /opt/java/11.0.14/Packages does not exist.

It seems like Oracle JDK 11.0.23 can make it possible but not OpenJDK 11.0.13.

[adietish]

@cloorc that's odd, can't explain why this would happen. A question for the folks that develop the java plugin for vscode. On the other hand, this being an intellij-plugin, it's advisable to build and run in intellij even though it should be possible to build & run in vscode I guess (gradle managing all the requirements)

[adietish]

[adietish]

There are limitations that were not implemented yet (ex. the list of events that kubectl is printing in the end of the output):

• Describe: describe events for a given pod #778
• Describe: Impl resource resolution for env vars #774
• Describe: display CSI Volume source attributes #776
• Describe: describe QOS for pods which dont have a QosClass property in status #777
• Describe: support other resources than pod #782

[cloorc]

@cloorc that's odd, can't explain why this would happen. A question for the folks that develop the java plugin for vscode. On the other hand, this being an intellij-plugin, it's advisable to build and run in intellij even though it should be possible to build & run in vscode I guess (gradle managing all the requirements)

That's make sense.My network is poor and GitHub just provides a codespace that can be used to develop any project online. So I tried it and found this issue. I Guess there's something wrong with Gradle Intellij Plugin working with VSCode. It mostly not a issue related to this project.