add kube-linter checks#214
add kube-linter checks#214openshift-merge-bot[bot] merged 12 commits intokonflux-workspaces:mainfrom sadlerap:kube-linter
Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Infra-deployments has a suite of checks that makes sure every kustomize manifest committed passes kube-linter in its default configuration. If we want to release onto platforms supported by infra-deployments, we need to be able to pass these checks too. This introduces a new check in CI to ensure that we don't fall out-of-line with what infra-deployments expects. Signed-off-by: Andy Sadler <ansadler@redhat.com>
Rather than pre-commit our image tags (which will likely get out-of-date very quickly), add in references to the built images during the packaging process. Signed-off-by: Andy Sadler <ansadler@redhat.com>
Signed-off-by: Andy Sadler <ansadler@redhat.com>
Signed-off-by: Andy Sadler <ansadler@redhat.com>
this information is already captured in github's security report, so it doesn't add anything useful. Signed-off-by: Andy Sadler <ansadler@redhat.com>
Signed-off-by: Andy Sadler <ansadler@redhat.com>
this was a debugging change that shouldn't have been committed Signed-off-by: Andy Sadler <ansadler@redhat.com>
Signed-off-by: Andy Sadler <ansadler@redhat.com>
don't know how that snuck in Signed-off-by: Andy Sadler <ansadler@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: filariow, sadlerap The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2 participants
Infra-deployments has a suite of checks that makes sure every kustomize manifest committed passes kube-linter in its default configuration. If we want to release onto platforms supported by infra-deployments, we need to be able to pass these checks too.
This introduces a new check in CI to ensure that we don't fall out-of-line with what infra-deployments expects.