Skip to content
This repository has been archived by the owner on Jul 4, 2024. It is now read-only.
/ score-helm Public archive

Score implementation for Helm (deprecated)

License

Notifications You must be signed in to change notification settings

score-spec/score-helm

Repository files navigation


⚠️ Deprecation Notice ⚠️

We have deprecated the score-helm CLI implementation. To get started with Score, we recommend using one of our reference implementations score-compose or score-k8s. If you're interested in developing a score-helm reference implementation, we'd love to support you! Please reach out to us for assistance and collaboration.


Score banner

Score Score overview

Score aims to improve developer producticity and experience by reducing the risk of configuration inconsistencies between local and remote environments. It provides developer-centric workload specification (score.yaml) which captures a workloads runtime requirements in a platform-agnostic manner. Learn more here.

The score.yaml specification file can be executed against a Score Implementation CLI, a conversion tool for application developers to generate environment specific configuration. In combination with environment specific parameters, the CLI tool can run your workload in the target environment by generating a platform-specific configuration file. The score-helm CLI is a reference implementation used to generate values.yaml files for your Helm chart.

Installation Installation

To install score-helm, follow the instructions as described in our installation guide.

Get Started Get Started

If you already have a score.yaml file defined, you can simply run the following command:

# Prepare a new Helm values file
score-helm run -f ./score.yaml -o ./values.yaml
  • run tells the CLI to translate the Score file to a Helm values.yaml file.
  • -f is the path to the Score file.
  • --env specifies the path to the values.yaml file.

If you're just getting started, follow this guide to run your first Hello World program with score-helm.

Get involved Get involved

Contributing Contributing

Contributions are what make the open-source community such a wonderful place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would improve this, please fork the repo and create a pull request. You can also open an issue with the tag enhancement.

  1. Fork the Project.
  2. Create your Feature Branch. git checkout -b feature/feature-name
  3. Commit your Changes. git commit -s -m "Add some AmazingFeature"
  4. Push to the Branch. git push origin feature/feature-name
  5. Open a Pull Request.

Read CONTRIBUTING for more information.

Documentation

You can find our documentation at docs.score.dev.

Roadmap

See Roadmap. You can submit an idea anytime.

License

License

Code of conduct

Contributor Covenant