FAQ

App CR ¶

This section covers questions for users directly using the App custom resource.

How can I control App CR reconciliation (pause, force, adjust frequency…)? ¶

You can set and unset spec.paused (example) or fiddle with spec.syncPeriod (example), which defaults to 30 seconds.

How can I tell which version of kapp-controller is installed? ¶

kapp-controller sets the annotation kapp-controller.carvel.dev/version on the deployment to the version deployed, so e.g. kubectl describe deployment kapp-controller -n kapp-controller | grep version will show the installed version.

Package Management CRs ¶

This section covers questions for users directly using the Package Management CRs custom resource.

How does kapp-controller handle PackageInstall when a PackageRepository is removed from the cluster? ¶

If a PackageInstall has been installed successfully from a Package that is part of a PackageRepository, and if that PacakgeRepository is ever deleted after the successful install, the PackageInstall will eventually report the following error: Reconcile failed: Expected to find at least one version, but did not. This error occurs due to the regular syncing of a PackageInstall with its Package.

Even though the error above is reported, the Package will still be installed and should work as expected. It can also still be uninstalled by deleting the PackageInstall. The PackageRepository can be recreated and the PackageInstall will sync and reconcile without any updates needed to resolve the error.

How can I generate the valuesSchema from my ytt schema? ¶

If you are using ytt as your Package’s templating option and have defined a schema, you can use ytt to generate your valuesSchema (which is in OpenAPI v3 format) for you.

This is the recommended workflow:

1. Create an OpenAPI Document from a Data Values Schema file:

   $ ytt -f schema.yml --data-values-schema-inspect -o openapi-v3 >schema-openapi.yml
   

   which will produce…

   #! schema-openapi.yml
   openapi: 3.0.0
   info:
     version: 1.0.0
     title: Openapi schema generated from ytt schema
   paths: {}
   components:
     schemas:
       dataValues:
         type: object
         properties:
           namespace:
             type: string
             default: fluent-bit
   

2. Turn your Package CR into a ytt template, so that you can insert the schema definition in the right spot, automatically:

   package-template.yml

   #@ load("@ytt:data", "data")
   #@ load("@ytt:yaml", "yaml")
   ...
   kind: Package
   spec:
     valuesSchema:
       openAPIv3:  #@ yaml.decode(data.values.openapi)["components"]["schemas"]["dataValues"]
   ...
   

   and render with the output from the ytt schema inspect:

   $ ytt -f package-template.yml --data-value-file openapi=schema-openapi.yml > package.yml
   

For more details, see:

• ytt: Export Schema in OpenAPI Format.
• ytt: Configuring Data Values via command line flags
• @ytt:yaml module