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

feat/custom analysis #474

Merged
merged 6 commits into from
Aug 4, 2024
Merged

feat/custom analysis #474

merged 6 commits into from
Aug 4, 2024

Conversation

AlexsJones
Copy link
Member

Closes #

πŸ“‘ Description

βœ… Checks

  • [x ] My pull request adheres to the code style of this project
  • [x ] My code requires changes to the documentation
  • [x ] I have updated the documentation as required
  • [ x] All the tests have passed

β„Ή Additional Information

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
@AlexsJones AlexsJones requested review from a team as code owners July 20, 2024 17:31
Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
JuHyung-Son
JuHyung-Son previously approved these changes Aug 3, 2024
@@ -54,9 +67,10 @@ func (c *Client) AddConfig(config *v1alpha1.K8sGPT) error {

func (c *Client) RemoveConfig(config *v1alpha1.K8sGPT) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this function actually work?
RemoveConfigRequest is actually an empty value.

Copy link
Member

@arbreezy arbreezy Aug 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RemoveConfig is actually only related to removing the cache configuration, frankly speaking the whole config API that we have created needs better structuring as it has grown organically including different functionality

It works by removing whatever is configured in the k8sgpt's configuration cache stanza..

So neither integrations nor now the customanalyzers will be deleted with removeConfig()

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah we were just discussing doing a refactor of the config stuff in slack

@arbreezy
Copy link
Member

arbreezy commented Aug 4, 2024

We also have to add the new crd schema to the helm templates and there are some conflicts

arbreezy
arbreezy previously approved these changes Aug 4, 2024
Signed-off-by: AlexsJones <alexsimonjones@gmail.com>
@AlexsJones AlexsJones dismissed stale reviews from arbreezy and JuHyung-Son via 04f70bb August 4, 2024 19:33
@AlexsJones AlexsJones merged commit f3173b5 into main Aug 4, 2024
7 checks passed
@AlexsJones AlexsJones deleted the feat/custom-analysis branch August 4, 2024 19:39
@AlexsJones AlexsJones restored the feat/custom-analysis branch August 4, 2024 19:39
@AlexsJones AlexsJones deleted the feat/custom-analysis branch August 4, 2024 19:39
ronaldpetty pushed a commit to ronaldpetty/k8sgpt-operator that referenced this pull request Aug 18, 2024
* chore: updated the spec

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>

* feat: add custom analyzers into the k8sgpt config

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>

* feat: add custom analyzers into the k8sgpt config

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>

* feat: add custom analyzers into the k8sgpt config

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>

* chore: fixed the reconcile not picking up custom analyzers

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>

---------

Signed-off-by: Alex Jones <alexsimonjones@gmail.com>
Signed-off-by: AlexsJones <alexsimonjones@gmail.com>
Signed-off-by: Ronald Petty <ronald.petty@rx-m.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants