lensapp/lens

Discovery based API support

Open

#666 opened on Aug 10, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (1,433 forks)batch import
bugenhancementhelp wanted

Repository metrics

Stars
 (22,003 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate how Lens currently handles Kubernetes API versioning and how a discovery mechanism could be implemented, e.g., by querying the API server's /apis endpoint or using kubectl. Consider the impact on error handling and user experience.
Tech stack
typescript
Domain
backendapidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
KubernetesTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40