Test-infra: Enable the slack reporter for k8s Prow Crier deployment

[clarketm]

What would you like to be added:
Enable the slack reporter for k8s Prow Crier deployment, ref: #14736.

slack reporter docs

Why is this needed:
Enhanced test failure awareness via Slack channel notification.

/help
/good-first-issue

[k8s-ci-robot]

@clarketm:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

What would you like to be added:
Enable the slack reporter for k8s Prow Crier deployment, ref: #14736

Why is this needed:
Enhanced test failure awareness via Slack channel notification.

/help
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[helderjs]

Hi!

@clarketm
I think I can help with this but I believe I need access to the cluster to create the secret (or someone needs to create it for me).

All the rest is about update https://github.com/kubernetes/test-infra/blob/6496538168bbd6a3aaa8b139a30d533a8943d2ee/prow/cluster/crier_deployment.yaml#L36 according to https://github.com/clarketm/kubernetes_test-infra/blob/b75a14a3781cc6b5b196b6d6328293a23938c2c1/prow/cmd/crier/README.md#slack-reporter

[clarketm]

Hi @helderjs,

I do not have full cluster access either. Please reach out to @cjwagner (or send a message to Kubernetes #testing-ops slack channel to solicit help regarding secret creation). There may already be a token in the cluster.

Regarding configuration, you are correct:

• [x] Update crier_deployment.yaml as delineated in the documentation.
• [x] Update config.yaml with slack reporter configuration. We can probably use the same configuration as Istio to start with.

[helderjs]

/assign

[helderjs]

@clarketm PR is done. I'm trying to get someone to create the secret in the cluster.

[BenTheElder]

https://github.com/kubernetes/test-infra/blob/e36eb04fdc6565d695a0086906ac5c92df7fb10b/prow/cluster/hook_deployment.yaml#L93

a token exists. need to verify that it's the correct one.

[clarketm]

@BenTheElder
You can verify the token here: https://api.slack.com/methods/chat.postMessage/test (this is the endpoint called by Crier). We will need to ensure the Slack test-failures channel exists as well.

[BenTheElder]

yep, that token works with that API

[helderjs]

@clarketm @BenTheElder is the name of the secret as I defined slack-token?
also what about the channel? should I ask someone to create the test-failures channel or change the config to something else?

[clarketm]

@clarketm @BenTheElder is the name of the secret as I defined slack-token?
also what about the channel? should I ask someone to create the test-failures channel or change the config to something else?

@BenTheElder verified the token; test-failures channel, like you have configured, is fine. Reach out to Slack #testing-ops regarding channel creation.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale