Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cloud66-oss/copper
A configuration file validator for Kubernetes.
https://github.com/cloud66-oss/copper
cloud66 configuration copper kubernetes validator
Last synced: 7 days ago
JSON representation
A configuration file validator for Kubernetes.
- Host: GitHub
- URL: https://github.com/cloud66-oss/copper
- Owner: cloud66-oss
- License: apache-2.0
- Created: 2018-03-20T11:00:27.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2022-06-11T15:59:48.000Z (over 2 years ago)
- Last Synced: 2024-04-05T22:33:59.779Z (7 months ago)
- Topics: cloud66, configuration, copper, kubernetes, validator
- Language: JavaScript
- Homepage: https://help.cloud66.com/copper/
- Size: 4.29 MB
- Stars: 272
- Watchers: 9
- Forks: 16
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-devsecops-russia - Copper
README
# Copper
Copper is a simple tool for validate your configuration files. This is specifically useful with Kubernetes configuration files to enforce best practices, apply policies and compliance requirements.
NOTE: This is Copper v2.0 which is a rewrite of Copper v1.0 (and not an in-place upgrade). Copper v2.0 uses Javascript as it's scripting language instead of Copper v1.0's custom DSL. At the moment, we don't offer any upgrades for old Copper v1 scripts to Copper v2.
- Help Pages: https://help.cloud66.com/copper/
- Slack Channel: [Join Our Slack Community](https://communityinviter.com/apps/cloud66ers/cloud-66-community).
- Articles: https://blog.cloud66.com/tag/copper/
## Installation
Head to the releases section of this repository and download the latest version of Copper. You can update Copper using `copper update` command at any time. By default, you will be running the `stable` releases. To change the channel, you can use the `--channel` argument in `copper update`.
## Usage
```bash
copper validate --in samples/sample.yml --validator samples/no_latest.js
```
This will run `no_latest.js` script to validate `sample.yml` (both available in this repository).
Copper supports YAML configuration files. By default, it loads the entire input YAML file into the `$$` variable that's available to your scripts. Each section of your YAML file is one item in the `$$` array.
Here is an example on how to stop using `latest` as the image tag.
```javascript
$$.forEach(function($){
if ($.kind === 'Deployment') {
$.spec.template.spec.containers.forEach(function(container) {
var image = new DockerImage(container.image);
if (image.tag === 'latest') {
errors.add_error('no_latest',"latest is used in " + $.metadata.name, 1)
}
});
}
});
```
As you can see, for each section in the YAML, we check if the item is a `Deployment`, if it is use one of Copper's internal helper classes `DocerkImage` to load the image name and parse it. `DockerImage` understands the intricacies of Docker image names (default tag names, default repos, etc). If the tag is `latest` we push an error into the `errors` list.
Once our script has run, Copper will check `errors` for any errors.
Each validation error should have 3 attributes:
`check_name`: The name of the check we just performed
`title`: Some explanation about this error
`severity`: A numerical representation of the severity of this error.
You can set the maximum allowed severity when running Copper using the `--threshold` argument.
### Helpers
To see what helpers are available for you to use in your scripts, see the files in the `libjs` folder in the repository. All these files are loaded before your script is run and therefore are available to use within your scripts.