-
Notifications
You must be signed in to change notification settings - Fork 75
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'onepassword/main' into add-hpa-pdb-affi…
…nity # Conflicts: # charts/connect/README.md # charts/connect/templates/connect-deployment.yaml # charts/connect/templates/operator-deployment.yaml
- Loading branch information
Showing
10 changed files
with
276 additions
and
113 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
# Contributing | ||
|
||
Thank you for your interest in contributing to the 1Password `connect-helm-chart` project 👋! We sincerely appreciate the time and effort you put into improving our Helm Charts. Before you start, please take a moment to read through this guide to understand our contribution process. | ||
|
||
## Getting Started | ||
|
||
To start contributing, get the latest [Helm release](https://github.com/helm/helm#install). | ||
|
||
## Testing | ||
|
||
NOTE: This only applies to changes made in `./charts/connect`. | ||
|
||
Run the following command to test changes made to the Connect Helm chart: | ||
|
||
``` | ||
helm test connect | ||
``` | ||
|
||
## Debugging | ||
|
||
- Running `helm lint` in the applicable subdirectory will verify that your chart follows best practices. | ||
|
||
- To run `helm template --debug`: | ||
|
||
1. navigate to the root of the repository | ||
2. `cd..` | ||
3. `helm template connect-helm-charts/charts/secrets-injector --debug` for **secrets-injector** OR `helm template connect-helm-charts/charts/connect --debug` for **connect**. | ||
|
||
For more debugging templates, feel free to consult the [docs](https://helm.sh/docs/chart_template_guide/debugging/). | ||
|
||
## Documentation Updates | ||
|
||
If adding a new configuration, update documentation for the tables in the [Connect README](./charts/connect/README.md) or in the [Secrets Injector README](./charts/secrets-injector/README.md) | ||
|
||
## Sign your commits | ||
|
||
To get your PR merged, we require you to sign your commits. | ||
|
||
### Sign commits with 1Password | ||
|
||
You can also sign commits using 1Password, which lets you sign commits with biometrics without the signing key leaving the local 1Password process. | ||
|
||
Learn how to use [1Password to sign your commits](https://developer.1password.com/docs/ssh/git-commit-signing/). | ||
|
||
### Sign commits with ssh-agent | ||
|
||
Follow the steps below to set up commit signing with `ssh-agent`: | ||
|
||
1. [Generate an SSH key and add it to ssh-agent](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) | ||
2. [Add the SSH key to your GitHub account](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) | ||
3. [Configure git to use your SSH key for commits signing](https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key#telling-git-about-your-ssh-key) | ||
|
||
### Sign commits with gpg | ||
|
||
Follow the steps below to set up commit signing with `gpg`: | ||
|
||
1. [Generate a GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key) | ||
2. [Add the GPG key to your GitHub account](https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account) | ||
3. [Configure git to use your GPG key for commits signing](https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key#telling-git-about-your-gpg-key) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,35 +1,54 @@ | ||
# 1Password Kubernetes Secrets Injector Helm chart | ||
|
||
## Installation | ||
|
||
Installing the Helm Chart with default configurations will deploy 1Password Kubernetes Secrets Injector in your default Namespace. | ||
|
||
``` | ||
helm install --generate-name 1password/secrets-injector | ||
``` | ||
|
||
## Configuration Values | ||
|
||
The 1Password Kubernetes Secrets Injector Helm chart offers many configuration options for deployment. Please refer to the list below for information on what configuration options are available as well as what the default configuration options are. | ||
|
||
[From the Official Helm Install Guide](https://helm.sh/docs/helm/helm_install/#helm-install): | ||
|
||
>To override values in a chart, use either the '--values' flag and pass in a file or use the '--set' flag and pass configuration from the command line, to force a string value use '--set-string'. In case a value is large and therefore you want not to use neither '--values' nor '--set', use '--set-file' to read the single large value from file. | ||
> To override values in a chart, use either the '--values' flag and pass in a file or use the '--set' flag and pass configuration from the command line, to force a string value use '--set-string'. In case a value is large and therefore you want not to use neither '--values' nor '--set', use '--set-file' to read the single large value from file. | ||
For example: | ||
|
||
For example: | ||
```bash | ||
$ helm install -f myvalues.yaml injector ./secrets-injector | ||
``` | ||
|
||
or | ||
or | ||
|
||
```bash | ||
$ helm install --set injector.applicationName=injector injector ./secrets-injector | ||
``` | ||
|
||
### Values | ||
| Key | Type | Default | Description | | ||
|-----|------|---------|-------------| | ||
| injector.applicationName | string | `"secrets-injector"` | The name of 1Password Kubernetes Secrets Injector Application | | ||
| injector.imagePullPolicy | string | `"IfNotPresent"` | The 1Password Secrets Injector docker image policy. `"IfNotPresent"` means the image is pulled only if it is not already present locally. | | ||
| injector.imageRepository | string | `"1password/kubernetes-secrets-injector"` | The 1Password Secrets Injector docker image repository | | ||
| injector.port | string | `443` | The port the Secrets Injector exposes | | ||
| injector.targetPort | integer | `8443` | The port the Secrets Injector API sends requests to the pod | | ||
| injector.version | string | `{{.Chart.AppVersion}}` | The 1Password Secrets Injector version to pull. | | ||
|
||
| Key | Type | Default | Description | | ||
| ------------------------ | ------- | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | ||
| injector.applicationName | string | `"secrets-injector"` | The name of 1Password Kubernetes Secrets Injector Application | | ||
| injector.imagePullPolicy | string | `"IfNotPresent"` | The 1Password Secrets Injector docker image policy. `"IfNotPresent"` means the image is pulled only if it is not already present locally. | | ||
| injector.imageRepository | string | `"1password/kubernetes-secrets-injector"` | The 1Password Secrets Injector docker image repository | | ||
| injector.port | string | `443` | The port the Secrets Injector exposes | | ||
| injector.targetPort | integer | `8443` | The port the Secrets Injector API sends requests to the pod | | ||
| injector.version | string | `{{.Chart.AppVersion}}` | The 1Password Secrets Injector version to pull. | | ||
| injector.customEnvVars | array | `[]` | Custom Environment Variables for the 1Password Secrets Injector container that are not specified in this helm chart. | | ||
|
||
#### Custom Environment Variables | ||
|
||
The injector container supports additional environment variables beyond those explicitly defined in the Helm chart. These can be defined using a key map for each custom variable. An example is shown below: | ||
|
||
```yaml | ||
injector: | ||
customEnvVars: | ||
- name: "CUSTOM_ENV_VAR1" | ||
value: "customvar2" | ||
- name: "CUSTOM_ENV_VAR2" | ||
value: "customvar2" | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters