You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched for similar issues and couldn't find anything matching
I've discussed this feature request in the K8sGPT Slack and got positive feedback
Is this feature request related to a problem?
No
Problem Description
At the current state, k8sgpt-operator is just tracking the cluster which is connected to.
I'd like to track remote clusters and store the resulting Result objects in the management one.
Solution Description
The k8sgpt resource could expose a new API field, named kubeconfig, pointing to a Secret object containing the kubeconfig that must be used to connect to the remote cluster.
The field spec.kubeconfig wouldn't be marked as mandatory, and when not specified, the k8sgpt deployment would use the ServiceAccount mounted to interact with the cluster where it's running.
When specified, the kubeconfig object will be mounted into the k8sgpt deployment object and consumed thanks to the --kubeconfig CLI argument (ref).
Benefits
With the rise of Cluster API is pretty common to have dozens of clusters. Rather than reconciling multiple times the k8sgpt operator instance across all the clusters, besides the security implications in sharing a sensitive data such as the API keys, this feature would allow to track misconfiguration of deployed clusters.
Potential Drawbacks
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Checklist
Is this feature request related to a problem?
No
Problem Description
At the current state, k8sgpt-operator is just tracking the cluster which is connected to.
I'd like to track remote clusters and store the resulting
Result
objects in the management one.Solution Description
The
k8sgpt
resource could expose a new API field, namedkubeconfig
, pointing to a Secret object containing the kubeconfig that must be used to connect to the remote cluster.The field
spec.kubeconfig
wouldn't be marked as mandatory, and when not specified, thek8sgpt
deployment would use theServiceAccount
mounted to interact with the cluster where it's running.When specified, the
kubeconfig
object will be mounted into thek8sgpt
deployment object and consumed thanks to the--kubeconfig
CLI argument (ref).Benefits
With the rise of Cluster API is pretty common to have dozens of clusters. Rather than reconciling multiple times the
k8sgpt
operator instance across all the clusters, besides the security implications in sharing a sensitive data such as the API keys, this feature would allow to track misconfiguration of deployed clusters.Potential Drawbacks
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: