Skip to content

Milestones

List view

  • In this milestone we will provide the rest of the functionality from the proposal - Add the alias, the ability to install the same package multiple times - Add the concept of optional package installation - Add the ability to the package author to inform a package can only be installed once or more times per cluster Link to proposal https://github.com/carvel-dev/carvel/blob/develop/proposals/kapp-controller/004-dependency-resolution/README.md

    No due date
  • In this milestone, we will enable the users to install packages with more than 1 level of dependencies - Create second level and further dependencies - Create a mechanism to support passing values to the second level and further dependencies Link to the proposal https://github.com/carvel-dev/carvel/blob/develop/proposals/kapp-controller/004-dependency-resolution/README.md

    No due date
  • In this milestone, we want to introduce the ability to add the following: - Introduce 'or' dependency - Add GVK dependency check - kctrl - Introduce ability to see or dependencies Link to proposal: https://github.com/carvel-dev/carvel/blob/develop/proposals/kapp-controller/004-dependency-resolution/README.md

    No due date
  • For the MVP of this feature, we expect to have the base for managing dependencies, so we will be able to do the following: - For this milestone, we will only support: - 1 level of dependencies - No `or` dependencies - Only Package dependencies using Semver - The Package Author can define dependencies in their Package - When the Package is installed, it will not reinstall packages that are already installed - When the Package is installed, it installs all the packages that are not yet installed - `kapp-controller` displays helpful status - Shows information about packages that are not available to be installed - When the installation is successful, it shows what package versions were installed and which ones were already in the cluster - When the user provides secrets to the dependent Package, the secret is passed along. This is only true for the Packages that will be installed. No changes will be made to packages already installed in the cluster. - Allow users to override the versions of dependent packages to be installed - `kctrl` - when getting package information, display dependencies associated with it - when installing a package, allow the user to provide, in a single file, the configuration for all the dependent packages Link to proposal https://github.com/carvel-dev/carvel/blob/develop/proposals/kapp-controller/004-dependency-resolution/README.md

    No due date