Glossary

  • Configuration management tool Link to concept page

    Score doesn’t specify any dns or route attribute values in the specification file.

    Those values may change based on the target environment, like testing, integration, or production

    For example, route table management is a configuration management task and Score isn’t a configuration management tool.

  • Configuration mismanagement Link to concept page

    Configuration mismanagement is the difference between how your local environment and remote environments are defined.

  • An Environment is a space where an instance of an Application can be deployed. It consists of a Kubernetes namespace and any shared Resources (as configured by relevant matching criteria).

  • Environment variables Link to concept page

    Environment-specific configuration allows the Score Specification file to be combined with variables to run Workloads in the target environment.

  • The resource section describes a Workload’s dependencies.

    This mechanism can be used to spin-up multi-service setups with docker compose.

  • Score implementation (CLI) Link to concept page

    The Score implementation (CLI) is the tooling used to convert the Score Specification into the target platform configuration file of your choice.

  • Score Specification Link to concept page

    The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It eliminates configuration mismanagement between environments.

  • A Workload is the code that runs in a Kubernetes cluster.

    It is commonly made up of one (or more) container and any configuration that is required.

  • Workload specification Link to concept page

    A Workload Specification file, or Workload Spec, is a single Workload specification file.