lensapp/lens

Discovery based API support

Open

#666 创建于 2020年8月10日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)TypeScript (22,003 star) (1,433 fork)batch import
bugenhancementhelp wanted

描述

What would you like to be added: A mechanism for cluster supported APIs to be discovered and handled automatically.

Why is this needed: Currently, our KubeApi<T> interface treats a version difference (say between v1beta1 and v1 of customresourcedefinition) as completely different apis and thus when trying to create a new CRD in lens unhelpful error messages are being displayed.

I don't know if this is a problem with other aspects of lens but it seems like definitely could be.

Possible Solutions:

  • Do nothing, keep manually adding apis as they come up
  • Add some sort of discovery mechanism that (might) request the supported APIs via kubectl or something similar.

贡献者指南

技术栈
typescriptreact
领域
backendapideveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of Kubernetes API versioningFamiliarity with Lens's KubeApi<T> interface
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
The issue proposes adding automatic discovery of supported APIs for Kubernetes clusters. To implement this, first explore the current KubeApi<T> interface in the Lens codebase to understand how API versions are handled. Then research how kubectl discovers API versions (e.g., via API discovery endpoints) and consider how to integrate that into Lens. The discussion suggests two possible solutions: manual addition or automatic discovery. The maintainers' input on preferred approach would be helpful.