[Feature]: Slack output

[AlexsJones]

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

In order to provide even more value to users we should give them ability to alert slack

e.g.

apiVersion: core.k8sgpt.ai/v1alpha1
kind: K8sGPT
metadata:
  name: k8sgpt-sample
  namespace: k8sgpt-operator-system
spec:
  model: gpt-3.5-turbo
  backend: openai
  noCache: false
  version: v0.3.0
  enableAI: true
  sinks:
   slack:
     webhook: <WEBHOOK>
  secret:
    name: k8sgpt-sample-secret
    key: openai-api-key

The idea is that this would let the user drop in a slack webhook to a pre-configured instance/channel

The main area for refactoring code would be here

I would suggest adding an additional sinks.Emit() style method and a new package pkg/sinks/slack where the sinks manager would have Slack as a registered sink type, we would also need a Configure method that is setup when the webhook is first detected on the CR

Benefits

Slack messages

Potential Drawbacks

No response

Additional Information

No response

[rakshitgondwal]

Hi, @AlexsJones! This sounds interesting to me. Would like to pick it up.

[AlexsJones]

Hi @rakshitgondwal, @arbreezy and I have discussed this and he will probably take on the initial implementation, but would you like to assist with that?

[rakshitgondwal]

Hi @rakshitgondwal, @arbreezy and I have discussed this and he will probably take on the initial implementation, but would you like to assist with that?

Yes! I'd like to learn more about this.

[agardnerIT]

#377 is a bit wider than this discussion. This thread only takes Slack into account. I'm wondering if we can generalise this for any web hook endpoint.

Further thought: Can we make this work for OAuth2 enabled endpoints (where there's a 2 step process to first retrieve a token then send the actual request). Slack (AFAIK) works on the API token (fire and forget), which IMO is simpler and nicer - but it seems that lots of people love OAuth2.

[arbreezy]

I don't see how we can generalise the endpoint cause the accepted json message may be different in slack, discord, MS teams so on and so forth. We can make a generic implementation which will make it easy to construct different json payloads based on the reporting provider.
WDYT ?