Skip to content

Expose securityContext on kanister-operator deployment to improve security #55

Expose securityContext on kanister-operator deployment to improve security

Expose securityContext on kanister-operator deployment to improve security #55

name: Triage Issues
permissions:
contents: read
on:
issues:
types:
- opened
- reopened
jobs:
triage:
if: github.repository == 'kanisterio/kanister'
name: Triage
permissions:
issues: write
runs-on: ubuntu-latest
steps:
-
name: Add label
uses: actions-ecosystem/action-add-labels@v1.1.3
with:
labels: "triage"
github_token: ${{ secrets.GITHUB_TOKEN }}
-
name: Add comment
uses: actions-ecosystem/action-create-comment@v1.0.2
if: github.event.action == 'opened'
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
body: |
Thanks for opening this issue :+1:. The team will review it shortly.
If this is a bug report, make sure to include clear instructions how on to reproduce the problem with [minimal reproducible examples](https://stackoverflow.com/help/minimal-reproducible-example), where possible. If this is a security report, please review our security policy as outlined in [SECURITY.md](https://github.com/kanisterio/kanister/blob/master/SECURITY.md).
If you haven't already, please take a moment to review our project's [Code of Conduct](https://github.com/kanisterio/kanister/blob/master/CODE_OF_CONDUCT.md) document.
-
name: Update project
uses: alex-page/github-project-automation-plus@v0.9.0
with:
repo-token: ${{ secrets.GH_TOKEN }} # must use a PAT here
project: Kanister
column: To Be Triaged