-
Notifications
You must be signed in to change notification settings - Fork 74
kc-agent usage lacks prerequisite and context explanation #6189
Copy link
Copy link
Closed
Labels
ai-fix-requestedhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.triage/neededNeeds triageNeeds triage
Description
Metadata
Metadata
Assignees
Labels
ai-fix-requestedhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.triage/neededNeeds triageNeeds triage
User Request
Type: bug
Target: Console Application
Submitted by: @rishi-jat
Console Request ID: 217873b3-8dd4-4914-8d5a-ecd7ed87a314
Description
Description:
The documentation introduces kc-agent installation without explaining prerequisites or usage context. It is unclear whether a Kubernetes cluster is required, what happens if a user does not have one, and whether the UI can be explored without setup.
Steps to reproduce:
This issue was automatically created from the KubeStellar Console.