Specifies list of components to enable used in direct mode (it respectively expects. Specifies type of the main workload resource Specifies whether the default workload resource is generated (Deployment/StatefulSet etc) Specifies the chart/application name (/name), since this is a generic chart Note: reuse uses only specific container keys such as image, command, env and others (i.e. Hello the command and other parameters are reused! # Many keys support interpolation! # sample.txt: |- some text file for release "-env ' resources: secrets.yaml # An arbitary configMap can be deployed # Note: the configMap name is prefixed with the "release name" # configMaps: Evidently such an installation might bring insufficient value to an enduser, thus this chart is charged with other resources (PR and add yours into the list :)).Īs of now dysnix/app chart ships the following resources: Just specify app.name and the image.repository and the deployment along with a couple of other resources (ServiceAccount namely) will be deployed straight away. The app chart basically generates a generic application based on the provided helm values input. Though unlike bitnami/template which requires generation and the development of a specific chart for your needs (totally viable approach), this chart brings a simplified approach which might be better suited for small teams - "define everything via helm values". Extensive value interface is tightgtly based on bitnami/template as well as its foundation this chart also relies on bitnami/common. eliminates "helm create & make a new chart again and again" cycle. This chart provides a generic interface to deploy an application straight away without necessity to create your own chart, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |