[incubator/anchore-engine] Adds incubator chart for Anchore Engine#3293
[incubator/anchore-engine] Adds incubator chart for Anchore Engine#3293k8s-ci-robot merged 9 commits intohelm:masterfrom
Conversation
|
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
DetailsInstructions 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. I understand the commands that are listed here. |
|
/assign @sameersbn |
|
/assign |
|
Working on the linter issues in the CircleCI result. Will update with commit to resolve those. |
|
/ok-to-test |
incubator/anchore-engine/Chart.yaml
Outdated
| email: zach@anchore.com | ||
| engine: gotpl | ||
| icon: https://anchore.com/wp-content/uploads/2016/08/anchore.png | ||
| appVersion: 0.1.3 |
There was a problem hiding this comment.
nit, but can you move this to just under the version above.
incubator/anchore-engine/README.md
Outdated
| ========================= | ||
|
|
||
| This chart deploys the Anchore Engine docker container image analysis system. Anchore Engine | ||
| requires a PostgresSQL database (>=9.6) which may be handled by the chart of supplied externally, |
|
|
||
| To get the service endpoint: | ||
|
|
||
| If using an ingress: |
There was a problem hiding this comment.
Can you conditionally template this in/out based on whether the ingress is enabled?
|
|
||
| or to use the IP instead of service dns name: | ||
|
|
||
| ANCHORE_CLI_URL=$(kubectl get svc --namespace {{ .Release.Namespace }} {{ template "fullname" . }} -o jsonpath="{.spec.clusterIP}")":{{.Values.service.ports.api}}/v1/" |
There was a problem hiding this comment.
Can you add a "smoke test" here? How do users know that Anchore is installed properly? What can they do with it once its installed? Maybe also point to the user docs.
|
/hold |
|
I have addressed the review suggestions and also added a commit to clean up some labelling issues in the deployment definitions to ensure things like 'kubectl get pods -l' filters behave as expected. |
|
Moved chart from incubator to stable for PR review per discussion with @viglesiasce |
|
Worked a treat! Thanks @zhill! /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: viglesiasce, zhill The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/hold cancel |
|
Thanks @viglesiasce ! |
Adds Anchore Engine chart to incubator.
To test the service you can hit the API (as described in the NOTES.txt) or use the anchore-cli to query the system. The cli is available here or via pip:
pip install anchorecli. The instructions in NOTES indicates how to configure the cli.