msb-public
/
helm
mirror of https://github.com/helm/helm
1
0
Code Issues Projects Releases Wiki Activity

s,kubernetes/charts,helm/charts,g (#4889)

Browse Source 
Signed-off-by: Matthew Fisher <matt.fisher@microsoft.com>
pull/4894/head
Matthew Fisher 6 years ago committed by GitHub
parent 00109db20a
commit 9dce1ac88b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
14 changed files with 96 additions and 96 deletions
Show Stats Download Patch File Download Diff File

6
docs/chart_repository.md
Unescape View File

@ -5,7 +5,7 @@ high level, a chart repository is a location where packaged charts can be
stored and shared. stored and shared.
The official chart repository is maintained by the The official chart repository is maintained by the
[Kubernetes Charts](https://github.com/kubernetes/charts), and we welcome [Helm Charts](https://github.com/helm/charts), and we welcome
participation. But Helm also makes it easy to create and run your own chart participation. But Helm also makes it easy to create and run your own chart
repository. This guide explains how to do so. repository. This guide explains how to do so.
@ -99,7 +99,7 @@ entries:
home: https://k8s.io/helm home: https://k8s.io/helm
name: nginx name: nginx
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- https://technosophos.github.io/tscharts/nginx-1.1.0.tgz - https://technosophos.github.io/tscharts/nginx-1.1.0.tgz
version: 1.1.0 version: 1.1.0
@ -143,7 +143,7 @@ Congratulations, now you have an empty GCS bucket ready to serve charts!
You may upload your chart repository using the Google Cloud Storage command line You may upload your chart repository using the Google Cloud Storage command line
tool, or using the GCS web UI. This is the technique the official Kubernetes tool, or using the GCS web UI. This is the technique the official Kubernetes
Charts repository hosts its charts, so you may want to take a Charts repository hosts its charts, so you may want to take a
[peek at that project](https://github.com/kubernetes/charts) if you get stuck. [peek at that project](https://github.com/helm/charts) if you get stuck.
**Note:** A public GCS bucket can be accessed via simple HTTPS at this address **Note:** A public GCS bucket can be accessed via simple HTTPS at this address
`https://bucket-name.storage.googleapis.com/`. `https://bucket-name.storage.googleapis.com/`.

2
docs/chart_template_guide/builtin_objects.md
Unescape View File

@ -31,5 +31,5 @@ In the previous section, we use `{{.Release.Name}}` to insert the name of a rele
The values are available to any top-level template. As we will see later, this does not necessarily mean that they will be available _everywhere_. The values are available to any top-level template. As we will see later, this does not necessarily mean that they will be available _everywhere_.
The built-in values always begin with a capital letter. This is in keeping with Go's naming convention. When you create your own names, you are free to use a convention that suits your team. Some teams, like the [Kubernetes Charts](https://github.com/kubernetes/charts) team, choose to use only initial lower case letters in order to distinguish local names from those built-in. In this guide, we follow that convention. The built-in values always begin with a capital letter. This is in keeping with Go's naming convention. When you create your own names, you are free to use a convention that suits your team. Some teams, like the [Helm Charts](https://github.com/helm/charts) team, choose to use only initial lower case letters in order to distinguish local names from those built-in. In this guide, we follow that convention.

2
docs/chart_template_guide/wrapping_up.md
Unescape View File

@ -4,7 +4,7 @@ This guide is intended to give you, the chart developer, a strong understanding
But there are many things this guide has not covered when it comes to the practical day-to-day development of charts. Here are some useful pointers to other documentation that will help you as you create new charts: But there are many things this guide has not covered when it comes to the practical day-to-day development of charts. Here are some useful pointers to other documentation that will help you as you create new charts:
- The [Kubernetes Charts project](https://github.com/kubernetes/charts) is an indispensable source of charts. That project is also sets the standard for best practices in chart development. - The [Helm Charts project](https://github.com/helm/charts) is an indispensable source of charts. That project is also sets the standard for best practices in chart development.
- The Kubernetes [User's Guide](http://kubernetes.io/docs/user-guide/) provides detailed examples of the various resource kinds that you can use, from ConfigMaps and Secrets to DaemonSets and Deployments. - The Kubernetes [User's Guide](http://kubernetes.io/docs/user-guide/) provides detailed examples of the various resource kinds that you can use, from ConfigMaps and Secrets to DaemonSets and Deployments.
- The Helm [Charts Guide](../charts.md) explains the workflow of using charts. - The Helm [Charts Guide](../charts.md) explains the workflow of using charts.
- The Helm [Chart Hooks Guide](../charts_hooks.md) explains how to create lifecycle hooks. - The Helm [Chart Hooks Guide](../charts_hooks.md) explains how to create lifecycle hooks.

58
docs/charts.md
Unescape View File

@ -114,7 +114,7 @@ to mark a chart as deprecated. If the **latest** version of a chart in the
repository is marked as deprecated, then the chart as a whole is considered to repository is marked as deprecated, then the chart as a whole is considered to
be deprecated. The chart name can later be reused by publishing a newer version be deprecated. The chart name can later be reused by publishing a newer version
that is not marked as deprecated. The workflow for deprecating charts, as that is not marked as deprecated. The workflow for deprecating charts, as
followed by the [kubernetes/charts](https://github.com/kubernetes/charts) followed by the [helm/charts](https://github.com/helm/charts)
project is: project is:
- Update chart's `Chart.yaml` to mark the chart as deprecated, bumping the - Update chart's `Chart.yaml` to mark the chart as deprecated, bumping the
version version
@ -142,9 +142,9 @@ for greater detail.
## Chart Dependencies ## Chart Dependencies
In Helm, one chart may depend on any number of other charts. In Helm, one chart may depend on any number of other charts.
These dependencies can be dynamically linked through the `requirements.yaml` These dependencies can be dynamically linked through the `requirements.yaml`
file or brought in to the `charts/` directory and managed manually. file or brought in to the `charts/` directory and managed manually.
Although manually managing your dependencies has a few advantages some teams need, Although manually managing your dependencies has a few advantages some teams need,
the preferred method of declaring dependencies is by using a the preferred method of declaring dependencies is by using a
@ -291,11 +291,11 @@ tags:
In the above example all charts with the tag `front-end` would be disabled but since the In the above example all charts with the tag `front-end` would be disabled but since the
`subchart1.enabled` path evaluates to 'true' in the parent's values, the condition will override the `subchart1.enabled` path evaluates to 'true' in the parent's values, the condition will override the
`front-end` tag and `subchart1` will be enabled. `front-end` tag and `subchart1` will be enabled.
Since `subchart2` is tagged with `back-end` and that tag evaluates to `true`, `subchart2` will be Since `subchart2` is tagged with `back-end` and that tag evaluates to `true`, `subchart2` will be
enabled. Also notes that although `subchart2` has a condition specified in `requirements.yaml`, there enabled. Also notes that although `subchart2` has a condition specified in `requirements.yaml`, there
is no corresponding path and value in the parent's values so that condition has no effect. is no corresponding path and value in the parent's values so that condition has no effect.
##### Using the CLI with Tags and Conditions ##### Using the CLI with Tags and Conditions
@ -317,19 +317,19 @@ helm install --set tags.front-end=true --set subchart2.enabled=false
#### Importing Child Values via requirements.yaml #### Importing Child Values via requirements.yaml
In some cases it is desirable to allow a child chart's values to propagate to the parent chart and be In some cases it is desirable to allow a child chart's values to propagate to the parent chart and be
shared as common defaults. An additional benefit of using the `exports` format is that it will enable future shared as common defaults. An additional benefit of using the `exports` format is that it will enable future
tooling to introspect user-settable values. tooling to introspect user-settable values.
The keys containing the values to be imported can be specified in the parent chart's `requirements.yaml` file The keys containing the values to be imported can be specified in the parent chart's `requirements.yaml` file
using a YAML list. Each item in the list is a key which is imported from the child chart's `exports` field. using a YAML list. Each item in the list is a key which is imported from the child chart's `exports` field.
To import values not contained in the `exports` key, use the [child-parent](#using-the-child-parent-format) format. To import values not contained in the `exports` key, use the [child-parent](#using-the-child-parent-format) format.
Examples of both formats are described below. Examples of both formats are described below.
##### Using the exports format ##### Using the exports format
If a child chart's `values.yaml` file contains an `exports` field at the root, its contents may be imported If a child chart's `values.yaml` file contains an `exports` field at the root, its contents may be imported
directly into the parent's values by specifying the keys to import as in the example below: directly into the parent's values by specifying the keys to import as in the example below:
```yaml ```yaml
@ -346,8 +346,8 @@ exports:
myint: 99 myint: 99
``` ```
Since we are specifying the key `data` in our import list, Helm looks in the `exports` field of the child Since we are specifying the key `data` in our import list, Helm looks in the `exports` field of the child
chart for `data` key and imports its contents. chart for `data` key and imports its contents.
The final parent values would contain our exported field: The final parent values would contain our exported field:
@ -358,16 +358,16 @@ myint: 99
``` ```
Please note the parent key `data` is not contained in the parent's final values. If you need to specify the Please note the parent key `data` is not contained in the parent's final values. If you need to specify the
parent key, use the 'child-parent' format. parent key, use the 'child-parent' format.
##### Using the child-parent format ##### Using the child-parent format
To access values that are not contained in the `exports` key of the child chart's values, you will need to To access values that are not contained in the `exports` key of the child chart's values, you will need to
specify the source key of the values to be imported (`child`) and the destination path in the parent chart's specify the source key of the values to be imported (`child`) and the destination path in the parent chart's
values (`parent`). values (`parent`).
The `import-values` in the example below instructs Helm to take any values found at `child:` path and copy them The `import-values` in the example below instructs Helm to take any values found at `child:` path and copy them
to the parent's values at the path specified in `parent:` to the parent's values at the path specified in `parent:`
```yaml ```yaml
@ -382,7 +382,7 @@ dependencies:
parent: myimports parent: myimports
``` ```
In the above example, values found at `default.data` in the subchart1's values will be imported In the above example, values found at `default.data` in the subchart1's values will be imported
to the `myimports` key in the parent chart's values as detailed below: to the `myimports` key in the parent chart's values as detailed below:
```yaml ```yaml
# parent's values.yaml file # parent's values.yaml file
@ -391,7 +391,7 @@ myimports:
myint: 0 myint: 0
mybool: false mybool: false
mystring: "helm rocks!" mystring: "helm rocks!"
``` ```
```yaml ```yaml
# subchart1's values.yaml file # subchart1's values.yaml file
@ -400,7 +400,7 @@ default:
data: data:
myint: 999 myint: 999
mybool: true mybool: true
``` ```
The parent chart's resulting values would be: The parent chart's resulting values would be:
@ -468,7 +468,7 @@ Furthermore, A is dependent on chart B that creates objects
- replicaset "B-ReplicaSet" - replicaset "B-ReplicaSet"
- service "B-Service" - service "B-Service"
After installation/upgrade of chart A a single Helm release is created/modified. The release will After installation/upgrade of chart A a single Helm release is created/modified. The release will
create/update all of the above Kubernetes objects in the following order: create/update all of the above Kubernetes objects in the following order:
- A-Namespace - A-Namespace
@ -478,16 +478,16 @@ create/update all of the above Kubernetes objects in the following order:
- A-Service - A-Service
- B-Service - B-Service
This is because when Helm installs/upgrades charts, This is because when Helm installs/upgrades charts,
the Kubernetes objects from the charts and all its dependencies are the Kubernetes objects from the charts and all its dependencies are
- aggregrated into a single set; then - aggregrated into a single set; then
- sorted by type followed by name; and then - sorted by type followed by name; and then
- created/updated in that order. - created/updated in that order.
Hence a single release is created with all the objects for the chart and its dependencies. Hence a single release is created with all the objects for the chart and its dependencies.
The install order of Kubernetes types is given by the enumeration InstallOrder in kind_sorter.go The install order of Kubernetes types is given by the enumeration InstallOrder in kind_sorter.go
(see [the Helm source file](https://github.com/helm/helm/blob/master/pkg/tiller/kind_sorter.go#L26)). (see [the Helm source file](https://github.com/helm/helm/blob/master/pkg/tiller/kind_sorter.go#L26)).
## Templates and Values ## Templates and Values
@ -560,8 +560,8 @@ It can use the following four template values (usually defined in a
All of these values are defined by the template author. Helm does not All of these values are defined by the template author. Helm does not
require or dictate parameters. require or dictate parameters.
To see many working charts, check out the [Kubernetes Charts To see many working charts, check out the [Helm Charts
project](https://github.com/kubernetes/charts) project](https://github.com/helm/charts)
### Predefined Values ### Predefined Values

8
docs/charts_tips_and_tricks.md
Unescape View File

@ -109,7 +109,7 @@ to render and exit when .Values.foo is undefined.
## Using the 'tpl' Function ## Using the 'tpl' Function
The `tpl` function allows developers to evaluate strings as templates inside a template. The `tpl` function allows developers to evaluate strings as templates inside a template.
This is useful to pass a template string as a value to a chart or render external configuration files. This is useful to pass a template string as a value to a chart or render external configuration files.
Syntax: `{{ tpl TEMPLATE_STRING VALUES }}` Syntax: `{{ tpl TEMPLATE_STRING VALUES }}`
Examples: Examples:
@ -152,7 +152,7 @@ imageCredentials:
registry: quay.io registry: quay.io
username: someone username: someone
password: sillyness password: sillyness
``` ```
We then define our helper template as follows: We then define our helper template as follows:
``` ```
@ -182,7 +182,7 @@ deployment spec itself didn't change the application keeps running
with the old configuration resulting in an inconsistent deployment. with the old configuration resulting in an inconsistent deployment.
The `sha256sum` function can be used to ensure a deployment's The `sha256sum` function can be used to ensure a deployment's
annotation section is updated if another file changes: annotation section is updated if another file changes:
```yaml ```yaml
kind: Deployment kind: Deployment
@ -232,7 +232,7 @@ by convention, helper templates and partials are placed in a
## Complex Charts with Many Dependencies ## Complex Charts with Many Dependencies
Many of the charts in the [official charts repository](https://github.com/kubernetes/charts) Many of the charts in the [official charts repository](https://github.com/helm/charts)
are "building blocks" for creating more advanced applications. But charts may be are "building blocks" for creating more advanced applications. But charts may be
used to create instances of large-scale applications. In such cases, a single used to create instances of large-scale applications. In such cases, a single
umbrella chart may have multiple subcharts, each of which functions as a piece umbrella chart may have multiple subcharts, each of which functions as a piece

6
docs/provenance.md
Unescape View File

@ -27,7 +27,7 @@ Prerequisites:
**NOTE:** If your PGP private key has a passphrase, you will be prompted to enter **NOTE:** If your PGP private key has a passphrase, you will be prompted to enter
that passphrase for any commands that support the `--sign` option. You can set the that passphrase for any commands that support the `--sign` option. You can set the
HELM_KEY_PASSPHRASE environment variable to that passphrase in case you don't want HELM_KEY_PASSPHRASE environment variable to that passphrase in case you don't want
to be prompted to enter the passphrase. to be prompted to enter the passphrase.
**NOTE:** The keyfile format for GnuPG changed in version 2.1. Prior to that release **NOTE:** The keyfile format for GnuPG changed in version 2.1. Prior to that release
@ -261,9 +261,9 @@ in using the provenance system:
- Keybase also has fabulous documentation available - Keybase also has fabulous documentation available
- While we haven't tested it, Keybase's "secure website" feature could - While we haven't tested it, Keybase's "secure website" feature could
be used to serve Helm charts. be used to serve Helm charts.
- The [official Kubernetes Charts project](https://github.com/kubernetes/charts) - The [official Helm Charts project](https://github.com/helm/charts)
is trying to solve this problem for the official chart repository. is trying to solve this problem for the official chart repository.
- There is a long issue there [detailing the current thoughts](https://github.com/kubernetes/charts/issues/23). - There is a long issue there [detailing the current thoughts](https://github.com/helm/charts/issues/23).
- The basic idea is that an official "chart reviewer" signs charts with - The basic idea is that an official "chart reviewer" signs charts with
her or his key, and the resulting provenance file is then uploaded her or his key, and the resulting provenance file is then uploaded
to the chart repository. to the chart repository.

2
docs/release_checklist.md
Unescape View File

@ -224,7 +224,7 @@ The community keeps growing, and we'd love to see you there!
- `#helm-users` for questions and just to hang out - `#helm-users` for questions and just to hang out
- `#helm-dev` for discussing PRs, code, and bugs - `#helm-dev` for discussing PRs, code, and bugs
- Hang out at the Public Developer Call: Thursday, 9:30 Pacific via [Zoom](https://zoom.us/j/696660622) - Hang out at the Public Developer Call: Thursday, 9:30 Pacific via [Zoom](https://zoom.us/j/696660622)
- Test, debug, and contribute charts: [GitHub/kubernetes/charts](https://github.com/kubernetes/charts) - Test, debug, and contribute charts: [GitHub/helm/charts](https://github.com/helm/charts)
## Installation and Upgrading ## Installation and Upgrading

18
docs/using_helm.md
Unescape View File

@ -63,7 +63,7 @@ stable/mysql 0.1.0 Chart for MySQL
stable/mariadb 0.5.1 Chart for MariaDB stable/mariadb 0.5.1 Chart for MariaDB
``` ```
Now you will only see the results that match your filter. Now you will only see the results that match your filter.
Why is Why is
`mariadb` in the list? Because its package description relates it to `mariadb` in the list? Because its package description relates it to
@ -231,7 +231,7 @@ There are two ways to pass configuration data during install:
If both are used, `--set` values are merged into `--values` with higher precedence. If both are used, `--set` values are merged into `--values` with higher precedence.
Overrides specified with `--set` are persisted in a configmap. Values that have been Overrides specified with `--set` are persisted in a configmap. Values that have been
`--set` can be viewed for a given release with `helm get values <release-name>`. `--set` can be viewed for a given release with `helm get values <release-name>`.
Values that have been `--set` can be cleared by running `helm upgrade` with `--reset-values` Values that have been `--set` can be cleared by running `helm upgrade` with `--reset-values`
specified. specified.
@ -405,11 +405,11 @@ is not a full list of cli flags. To see a description of all flags, just run
This defaults to 300 (5 minutes) This defaults to 300 (5 minutes)
- `--wait`: Waits until all Pods are in a ready state, PVCs are bound, Deployments - `--wait`: Waits until all Pods are in a ready state, PVCs are bound, Deployments
have minimum (`Desired` minus `maxUnavailable`) Pods in ready state and have minimum (`Desired` minus `maxUnavailable`) Pods in ready state and
Services have an IP address (and Ingress if a `LoadBalancer`) before Services have an IP address (and Ingress if a `LoadBalancer`) before
marking the release as successful. It will wait for as long as the marking the release as successful. It will wait for as long as the
`--timeout` value. If timeout is reached, the release will be marked as `--timeout` value. If timeout is reached, the release will be marked as
`FAILED`. Note: In scenario where Deployment has `replicas` set to 1 and `FAILED`. Note: In scenario where Deployment has `replicas` set to 1 and
`maxUnavailable` is not set to 0 as part of rolling update strategy, `maxUnavailable` is not set to 0 as part of rolling update strategy,
`--wait` will return as ready as it has satisfied the minimum Pod in ready condition. `--wait` will return as ready as it has satisfied the minimum Pod in ready condition.
- `--no-hooks`: This skips running hooks for the command - `--no-hooks`: This skips running hooks for the command
- `--recreate-pods` (only available for `upgrade` and `rollback`): This flag - `--recreate-pods` (only available for `upgrade` and `rollback`): This flag
@ -518,8 +518,8 @@ $ helm install ./deis-workflow-0.1.0.tgz
Charts that are archived can be loaded into chart repositories. See the Charts that are archived can be loaded into chart repositories. See the
documentation for your chart repository server to learn how to upload. documentation for your chart repository server to learn how to upload.
Note: The `stable` repository is managed on the [Kubernetes Charts Note: The `stable` repository is managed on the [Helm Charts
GitHub repository](https://github.com/kubernetes/charts). That project GitHub repository](https://github.com/helm/charts). That project
accepts chart source code, and (after audit) packages those for you. accepts chart source code, and (after audit) packages those for you.
## Tiller, Namespaces and RBAC ## Tiller, Namespaces and RBAC

2
pkg/downloader/testdata/helmhome/repository/cache/testing-basicauth-index.yaml vendored
Unescape View File

@ -8,7 +8,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- http://username:password@example.com/foo-1.2.3.tgz - http://username:password@example.com/foo-1.2.3.tgz
version: 1.2.3 version: 1.2.3

2
pkg/downloader/testdata/helmhome/repository/cache/testing-https-index.yaml vendored
Unescape View File

@ -8,7 +8,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- https://example.com/foo-1.2.3.tgz - https://example.com/foo-1.2.3.tgz
version: 1.2.3 version: 1.2.3

2
pkg/downloader/testdata/helmhome/repository/cache/testing-index.yaml vendored
Unescape View File

@ -36,7 +36,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- http://example.com/foo-1.2.3.tgz - http://example.com/foo-1.2.3.tgz
version: 1.2.3 version: 1.2.3

4
pkg/downloader/testdata/helmhome/repository/cache/testing-relative-index.yaml vendored
Unescape View File

@ -8,7 +8,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- charts/foo-1.2.3.tgz - charts/foo-1.2.3.tgz
version: 1.2.3 version: 1.2.3
@ -21,7 +21,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- bar-1.2.3.tgz - bar-1.2.3.tgz
version: 1.2.3 version: 1.2.3

4
pkg/downloader/testdata/helmhome/repository/cache/testing-relative-trailing-slash-index.yaml vendored
Unescape View File

@ -8,7 +8,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- charts/foo-1.2.3.tgz - charts/foo-1.2.3.tgz
version: 1.2.3 version: 1.2.3
@ -21,7 +21,7 @@ entries:
keywords: [] keywords: []
maintainers: [] maintainers: []
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- bar-1.2.3.tgz - bar-1.2.3.tgz
version: 1.2.3 version: 1.2.3

76
pkg/getter/testdata/repository/cache/stable-index.yaml vendored
Unescape View File

@ -214,7 +214,7 @@ entries:
name: concourse name: concourse
sources: sources:
- https://github.com/concourse/bin - https://github.com/concourse/bin
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/concourse-0.1.3.tgz - https://kubernetes-charts.storage.googleapis.com/concourse-0.1.3.tgz
version: 0.1.3 version: 0.1.3
@ -234,7 +234,7 @@ entries:
name: concourse name: concourse
sources: sources:
- https://github.com/concourse/bin - https://github.com/concourse/bin
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/concourse-0.1.2.tgz - https://kubernetes-charts.storage.googleapis.com/concourse-0.1.2.tgz
version: 0.1.2 version: 0.1.2
@ -254,7 +254,7 @@ entries:
name: concourse name: concourse
sources: sources:
- https://github.com/concourse/bin - https://github.com/concourse/bin
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/concourse-0.1.1.tgz - https://kubernetes-charts.storage.googleapis.com/concourse-0.1.1.tgz
version: 0.1.1 version: 0.1.1
@ -273,7 +273,7 @@ entries:
name: concourse name: concourse
sources: sources:
- https://github.com/concourse/bin - https://github.com/concourse/bin
- https://github.com/kubernetes/charts - https://github.com/helm/charts
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/concourse-0.1.0.tgz - https://kubernetes-charts.storage.googleapis.com/concourse-0.1.0.tgz
version: 0.1.0 version: 0.1.0
@ -3985,7 +3985,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.6.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.6.tgz
@ -4006,7 +4006,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.5.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.5.tgz
@ -4025,7 +4025,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.4.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.4.tgz
@ -4044,7 +4044,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.3.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.3.tgz
@ -4063,7 +4063,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.2.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.2.tgz
@ -4082,7 +4082,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.1.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.1.tgz
@ -4101,7 +4101,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.2.0.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.2.0.tgz
@ -4120,7 +4120,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.1.2.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.1.2.tgz
@ -4139,7 +4139,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.1.1.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.1.1.tgz
@ -4158,7 +4158,7 @@ entries:
name: Vic Iglesias name: Vic Iglesias
name: mysql name: mysql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/mysql - https://github.com/docker-library/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/mysql-0.1.0.tgz - https://kubernetes-charts.storage.googleapis.com/mysql-0.1.0.tgz
@ -5034,7 +5034,7 @@ entries:
name: Patrick Galbraith name: Patrick Galbraith
name: percona name: percona
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/percona - https://github.com/docker-library/percona
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/percona-0.1.0.tgz - https://kubernetes-charts.storage.googleapis.com/percona-0.1.0.tgz
@ -5404,7 +5404,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.6.0.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.6.0.tgz
@ -5426,7 +5426,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.5.1.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.5.1.tgz
@ -5448,7 +5448,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.5.0.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.5.0.tgz
@ -5470,7 +5470,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.4.0.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.4.0.tgz
@ -5492,7 +5492,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.4.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.4.tgz
@ -5512,7 +5512,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.3.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.3.tgz
@ -5532,7 +5532,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.2.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.2.tgz
@ -5552,7 +5552,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.1.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.1.tgz
@ -5572,7 +5572,7 @@ entries:
- name: databus23 - name: databus23
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.0.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.3.0.tgz
@ -5591,7 +5591,7 @@ entries:
- name: swordbeta - name: swordbeta
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.2.2.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.2.2.tgz
@ -5610,7 +5610,7 @@ entries:
- name: swordbeta - name: swordbeta
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.2.1.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.2.1.tgz
@ -5629,7 +5629,7 @@ entries:
- name: swordbeta - name: swordbeta
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.2.0.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.2.0.tgz
@ -5648,7 +5648,7 @@ entries:
- name: swordbeta - name: swordbeta
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.1.1.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.1.1.tgz
@ -5667,7 +5667,7 @@ entries:
- name: swordbeta - name: swordbeta
name: postgresql name: postgresql
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/docker-library/postgres - https://github.com/docker-library/postgres
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/postgresql-0.1.0.tgz - https://kubernetes-charts.storage.googleapis.com/postgresql-0.1.0.tgz
@ -6720,7 +6720,7 @@ entries:
sources: sources:
- https://bitbucket.org/sapho/ops-docker-tomcat/src - https://bitbucket.org/sapho/ops-docker-tomcat/src
- https://hub.docker.com/r/sapho/ops-docker-tomcat - https://hub.docker.com/r/sapho/ops-docker-tomcat
- https://github.com/kubernetes/charts/tree/master/stable/mysql - https://github.com/helm/charts/tree/master/stable/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/sapho-0.1.5.tgz - https://kubernetes-charts.storage.googleapis.com/sapho-0.1.5.tgz
version: 0.1.5 version: 0.1.5
@ -6738,7 +6738,7 @@ entries:
sources: sources:
- https://bitbucket.org/sapho/ops-docker-tomcat/src - https://bitbucket.org/sapho/ops-docker-tomcat/src
- https://hub.docker.com/r/sapho/ops-docker-tomcat - https://hub.docker.com/r/sapho/ops-docker-tomcat
- https://github.com/kubernetes/charts/tree/master/stable/mysql - https://github.com/helm/charts/tree/master/stable/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/sapho-0.1.4.tgz - https://kubernetes-charts.storage.googleapis.com/sapho-0.1.4.tgz
version: 0.1.4 version: 0.1.4
@ -6756,7 +6756,7 @@ entries:
sources: sources:
- https://bitbucket.org/sapho/ops-docker-tomcat/src - https://bitbucket.org/sapho/ops-docker-tomcat/src
- https://hub.docker.com/r/sapho/ops-docker-tomcat - https://hub.docker.com/r/sapho/ops-docker-tomcat
- https://github.com/kubernetes/charts/tree/master/stable/mysql - https://github.com/helm/charts/tree/master/stable/mysql
urls: urls:
- https://kubernetes-charts.storage.googleapis.com/sapho-0.1.3.tgz - https://kubernetes-charts.storage.googleapis.com/sapho-0.1.3.tgz
version: 0.1.3 version: 0.1.3
@ -6794,7 +6794,7 @@ entries:
name: Shane Starcher name: Shane Starcher
name: sensu name: sensu
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/sstarcher/docker-sensu - https://github.com/sstarcher/docker-sensu
- https://github.com/sensu/sensu - https://github.com/sensu/sensu
urls: urls:
@ -6815,7 +6815,7 @@ entries:
name: Shane Starcher name: Shane Starcher
name: sensu name: sensu
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/sstarcher/docker-sensu - https://github.com/sstarcher/docker-sensu
- https://github.com/sensu/sensu - https://github.com/sensu/sensu
urls: urls:
@ -6836,7 +6836,7 @@ entries:
name: Shane Starcher name: Shane Starcher
name: sensu name: sensu
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/sstarcher/docker-sensu - https://github.com/sstarcher/docker-sensu
- https://github.com/sensu/sensu - https://github.com/sensu/sensu
urls: urls:
@ -7506,7 +7506,7 @@ entries:
name: Shane Starcher name: Shane Starcher
name: uchiwa name: uchiwa
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/sstarcher/docker-uchiwa - https://github.com/sstarcher/docker-uchiwa
- https://github.com/sensu/uchiwa - https://github.com/sensu/uchiwa
urls: urls:
@ -7528,7 +7528,7 @@ entries:
name: Shane Starcher name: Shane Starcher
name: uchiwa name: uchiwa
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/sstarcher/docker-uchiwa - https://github.com/sstarcher/docker-uchiwa
- https://github.com/sensu/uchiwa - https://github.com/sensu/uchiwa
urls: urls:
@ -7550,7 +7550,7 @@ entries:
name: Shane Starcher name: Shane Starcher
name: uchiwa name: uchiwa
sources: sources:
- https://github.com/kubernetes/charts - https://github.com/helm/charts
- https://github.com/sstarcher/docker-uchiwa - https://github.com/sstarcher/docker-uchiwa
- https://github.com/sensu/uchiwa - https://github.com/sensu/uchiwa
urls: urls:

Write Preview
Loading…
Cancel
Save