feat: add storage, RBAC, and custom resource tools#129
Merged
Conversation
basebandit
force-pushed
the
feat/storage-rbac-crd
branch
from
983ab8d to
bcdd50a
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
list/get/deletePersistentVolumes;create/list/get/deletePersistentVolumeClaims;list/getStorageClasses. Adds
PVCParamstotypes.go.list/getfor Roles, RoleBindings, ClusterRoles, ClusterRoleBindings, ServiceAccounts.list/getCRDs, genericlist/getof custom resources by group/version/resource via thedynamic client, and
list_api_resourcesfor API discovery.Why
The roadmap listed Storage, RBAC, Custom Resources, and API Discovery as unimplemented. Operators running Kai in-cluster
could not inspect volumes, audit RBAC, or work with CRDs — the core gaps blocking a complete cluster-management story.
This lands those resource types using the existing 6-touchpoint tool pattern (post-#123 mcp-go v0.52 API), with MCP
annotations (ReadOnlyHint for list/get, DestructiveHint for delete) so clients can reason about tool safety.
Test plan
go build ./...go vet ./...go test -race ./...(cluster + tools green; new-code coverage ~86%)