ef59f7c26e
* Add Github Action from https://github.com/mambax/setup-polaris * Add tag information to action * repository name must be lowercase * repository name must be lowercase * repository name must be lowercase * Own image * Debug * Make the file local * Move into actions folder * Rename action * Remove path slash * Rename Dockerfile * Change path * Move script * Remove dot * Test * - Change to gh/download setup script - Move docs into Infra as Code page * Add small comment about Dockerfile * Rm unwanted line break * Improve action yaml * Update test_setup.yml * Update test_setup.yml * Update test_setup.yml * Pavel fixed all bugs Co-authored-by: dom <dominik.meyer01@sap.com> Co-authored-by: Pavel Zorin <pazonec@yandex.ru>
2.0 KiB
Infrastructure as Code
Want to see results for all your IaC repos in one place? Check out Fairwinds Insights
Polaris can be used on the command line to audit local Kubernetes manifests stored in YAML files. This is particularly helpful for running Polaris against your infrastructure-as-code as part of a CI/CD pipeline. Use the available command line flags to cause CI/CD to fail if your Polaris score drops below a certain threshold, or if any danger-level issues arise.
Install the CLI
To run Polaris against your YAML manifests, e.g. as part of a Continuous Integration process, you'll need to install the CLI.
Binary releases can be downloaded from the releases page or can be installed with Homebrew:
brew tap FairwindsOps/tap
brew install FairwindsOps/tap/polaris
polaris version
Running in a CI pipeline
You can tell the CLI to set an exit code if it detects certain issues with your YAML files. For example, to fail if polaris detects any danger-level issues, or if the score drops below 90%:
polaris audit --audit-path ./deploy/ \
--set-exit-code-on-danger \
--set-exit-code-below-score 90
As Github Action
Setup polaris action
This action downloads a version of polaris and adds it to the path. It makes the polaris cli ready to use in following steps of the same job.
Inputs
version
The release version to fetch. This has to be in the form <tag_name>.
Outputs
version
The version number of the release tag.
Example usage
uses: fairwindsops/polaris@master
with:
version: "3.0.3"
Example inside a job:
steps:
- uses: actions/checkout@v2
- name: Setup polaris
uses: fairwindsops/polaris@master
with:
version: 3.0.3
- name: Use command
run: polaris version