API stability
KubeGlass is before 1.0. Until 1.0, follow these rules of thumb.
What is meant to stay stable
Section titled “What is meant to stay stable”- Configuration: setting names, environment variables and Helm values. If one has to change, the old name keeps working for at least one minor release and the release notes say what to use instead.
- Command line:
kubeglass, its flags, andkubeglass mcp. - MCP tool names and their arguments. New tools and new optional arguments may appear.
- Error codes in the
errorfield of API errors. New codes may appear; existing ones keep their meaning.
What can change
Section titled “What can change”The HTTP API under /api/v1/ exists for the UI. Endpoints, parameters and response fields can change in any minor release before 1.0, and the release notes list changes that break callers. If you build on it, pin a version, or use the MCP server, which is designed for other programs.
Human-readable messages, log lines and the UI itself can change at any time.
After 1.0
Section titled “After 1.0”From 1.0 on, KubeGlass follows semantic versioning: breaking changes to the configuration, command line, MCP tools or documented API endpoints only happen in a major release, after a deprecation in an earlier minor release.