-
Notifications
You must be signed in to change notification settings - Fork 2.9k
[Docs] Add Kubernetes cluster permissions guide #16649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: aabidsofi19 <65964225+aabidsofi19@users.noreply.github.com>
|
|
| --- | ||
| layout: default | ||
| title: Kubernetes Cluster Permissions | ||
| permalink: reference/kubernetes-cluster-permissions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot find an alternate location in Meshery Docs outside of the reference section for this information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved the documentation to guides/infrastructure-management/kubernetes-cluster-permissions.md and placed it under the "Managing Connections" section in the Infrastructure Management guides. This location is more appropriate as it's directly related to connecting and managing Kubernetes clusters. All internal references have been updated. (19b53b5)
…nt guides Co-authored-by: leecalcote <7570704+leecalcote@users.noreply.github.com>
|
🚀 Preview for commit d9e7b9c at: https://6942931a465431137964b3e7--meshery-docs-preview.netlify.app |
Meshery requires specific kubeconfig permissions to connect to and manage Kubernetes clusters, but these requirements were undocumented. At minimum, read access to
kube-systemnamespace is required for cluster identification.Changes
New Infrastructure Management Guide
kubernetes-cluster-permissions.md: Comprehensive guide covering minimum and full management permissions, complete RBAC examples, permission levels for different use cases, security considerations, and troubleshooting guideguides/infrastructure-management/as a grandchild under "Managing Connections" for better discoverabilityKey Content Areas
kube-systemnamespace (Meshery uses the namespace UID as unique cluster identifier)Integration Points
quick-start.mdwith permissions alert in cluster connection sectionkubernetes.mdprerequisites to reference permissions documentationlifecycle-management.mdwith Kubernetes permissions noticetoc.ymlunder Infrastructure Management → Managing ConnectionsTechnical Basis
Analysis of connection handling code confirmed:
server/models/k8s_context.go: Querieskube-systemnamespace UID for cluster identificationserver/models/meshery_controllers.go: Deploys Operator tomesherynamespace by defaultOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.