Skip to content
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

[Feature]: Support remote cache through API #449

Closed
2 tasks done
AlexsJones opened this issue May 22, 2023 · 4 comments · Fixed by #459
Closed
2 tasks done

[Feature]: Support remote cache through API #449

AlexsJones opened this issue May 22, 2023 · 4 comments · Fixed by #459

Comments

@AlexsJones
Copy link
Member

Checklist

  • 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

No response

Solution Description

Relates to k8sgpt-ai/k8sgpt-operator#113 and supporting the remote cache through the operator - we need a way to program it on an analyze request.

Benefits

N/A

Potential Drawbacks

No response

Additional Information

No response

@matthisholleville
Copy link
Contributor

Shoudn't we add new api route for cache configuration instead add more complexity on analyze request ?

@AlexsJones
Copy link
Member Author

Shoudn't we add new api route for cache configuration instead add more complexity on analyze request ?

Probably a good idea yes, I would imagine we're at the point for a general configuration route

@matthisholleville
Copy link
Contributor

The only question I have pending is: "How do we handle cache deletion through the operator?"

@AlexsJones
Copy link
Member Author

AlexsJones commented May 22, 2023

Removal of the K8sGPT object? seems pretty easy to do - yes this would mean the operator has the AWS sdk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants