Community: REQUEST: Kubernetes slack `incoming webhook` URL
GitHub Username:
@hongkailiu @stevekuznetsov
Slack Username:
@hongkailiu @stevekuznetsov
What Type of Request is it (Channel, User Group, Bot, Token, or Webhook)?
We need slack incoming-webhooks URL to set up alertmanager of prow-monitoring stack.
Name of Requested Resource:
Description of Request:
When we get the URL, we will do kubectl apply -f using the secret file.
hongkailiu
All 7 comments
/assign @Katharine
hongkailiu
on 17 Jul 2019
Putting on my sig-testing hat:
We want to create a slack app that has an incoming webhook, for the purpose of being able to send alerts about the health of prow. Contrary to the documentation and purpose of incoming webhooks, the slack app will be theoretically capable of sending to _any_ channel (because what even is slack??). In practice, however, it will not send to many.
The only scope used is the webhook, which is strictly write-only, so the token cannot be used to retrieve information about anything in Slack. It will live in the prow cluster, which also contains other far greater secrets.
Putting on my slack admin hat:
This seems reasonable to me — the code is open source (though not actually written by us), is running in a sig-testing cluster, and serves an obviously useful purpose, so +1 from me.
Katharine
on 17 Jul 2019
+1
jeefy
on 17 Jul 2019
I've created the integration and added the webhook URL secret into the prow cluster.
/close
Katharine
on 17 Jul 2019
@Katharine: Closing this issue.
In response to this:
I've created the integration and added the webhook URL secret into the prow cluster.
/close
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.
k8s-ci-robot
on 17 Jul 2019
Thanks @Katharine :)
/pony yay
mrbobbytables
on 17 Jul 2019
@mrbobbytables:
In response to this:
Thanks @Katharine :)
/pony yay
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.
k8s-ci-robot
on 17 Jul 2019
Related issues
casusbelli
·
4Comments
parispittman
·
3Comments
jamiehannaford
·
3Comments
justaugustus
·
5Comments
bboreham
·
4Comments
Most helpful comment
Putting on my sig-testing hat:
We want to create a slack app that has an incoming webhook, for the purpose of being able to send alerts about the health of prow. Contrary to the documentation and purpose of incoming webhooks, the slack app will be theoretically capable of sending to _any_ channel (because what even is slack??). In practice, however, it will not send to many.
The only scope used is the webhook, which is strictly write-only, so the token cannot be used to retrieve information about anything in Slack. It will live in the prow cluster, which also contains other far greater secrets.
Putting on my slack admin hat:
This seems reasonable to me — the code is open source (though not actually written by us), is running in a sig-testing cluster, and serves an obviously useful purpose, so +1 from me.