![]() NOTE: Kubernetes annotations cannot be booleans and must be strings, so make sure to quote this. When this annotation is present on a resource and evaluates to 'true', the resource will not be included in the kustomization.yaml file and will not be written to disk. If both are present, the kots.io/exclude annotation will be applied, and the kots.io/when annotation will be ignored. Only one of the following annotations can be present on a resource. Replīy default, if neither kots.io/exclude nor kots.io/when annotations are present on a resource, the resource will be included. ![]() Use case: Providing custom Ingress annotations for a customer-provided Ingress controller. The app manager uses placeholder annotations as a way to provide an annotation that may not appear in the final rendered YAML. App Manager Annotations Placeholder Annotation To provide optional resource installation, the app manager uses annotations and template functions to conditionally include or exclude resources. This means that the customer-supplied configuration input values may result in optional Kubernetes manifests that should not be installed. In this scenario, when a customer chooses to bring their own database, it is not desirable to deploy the optional database resources (StatefulSet, Service, etc.). A common example is giving the customer the choice to install a new database or use an existing database. Often, vendors need a way to optionally install resources depending on customers configuration choices. Including Optional and Conditional Resources
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |