Skip to content

Commit 3325f46

Browse files
gprosslinerarttor
authored andcommitted
removed ImagePullSecrets section
1 parent 3db00d1 commit 3325f46

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

README.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -74,21 +74,7 @@ Usage:
7474
| -vv | Enable very verbose output. Also prints DEBUG. | `helmify -vv`|
7575
| -version | Print helmify version. | `helmify -version`|
7676
| -crd-dir | Place crds in their own folder per Helm 3 [docs](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you). Caveat: CRDs templating is not supported by Helm. | `helmify -crd-dir`|
77-
| -image-pull-secrets| Allows the user to use existing secrets as imagePullSecrets | `helmify -image-pull-secrets`|
78-
79-
## ImagePullSecrets
80-
81-
If no `imagePullSecrets` are present in the input manifests, helmify allows existing
82-
secrets to be used as `imagePullSecrets` for pods in deployments and daemonsets.
83-
84-
You need to enable this feature by the `-image-pull-secrets` flag. This allows
85-
the user to add existing secrets in `values.yaml` like:
86-
87-
```yaml
88-
# values.yaml
89-
imagePullSecrets:
90-
- name: image-pull-secret
91-
```
77+
| -image-pull-secrets| Allows the user to use existing secrets as imagePullSecrets | `helmify -image-pull-secrets`|
9278

9379
## Status
9480
Supported k8s resources:

0 commit comments

Comments
 (0)