Skip to content

Commit

Permalink
github_actions_ci: Update public key
Browse files Browse the repository at this point in the history
  • Loading branch information
draios-jenkins committed Jul 20, 2023
1 parent 4796158 commit 209c438
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 28 deletions.
15 changes: 6 additions & 9 deletions charts/admission-controller/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ $ pre-commit run -a
$ helm repo add sysdig https://charts.sysdig.com
$ helm repo update
$ helm upgrade --install sysdig-admission-controller sysdig/admission-controller \
--create-namespace -n sysdig-admission-controller --version=0.11.4 \
--create-namespace -n sysdig-admission-controller --version=0.11.5 \
--set clusterName=CLUSTER_NAME \
--set sysdig.secureAPIToken=SECURE_API_TOKEN
```
Expand Down Expand Up @@ -55,7 +55,7 @@ This chart deploys the Sysdig Admission Controller on a [Kubernetes](http://kube
To install the chart with the release name `admission-controller`:

```console
$ helm upgrade --install sysdig-admission-controller sysdig/admission-controller -n sysdig-admission-controller --version=0.11.4
$ helm upgrade --install sysdig-admission-controller sysdig/admission-controller -n sysdig-admission-controller --version=0.11.5
```

The command deploys the Sysdig Admission Controller on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
Expand Down Expand Up @@ -143,10 +143,7 @@ The following table lists the configurable parameters of the `admission-controll
| webhook.dryRun | Dry Run request | <code>false</code> |
| webhook.logLevel | Log Level - Valid Values are: error, info, debug, trace | <code>info</code> |
| webhook.ssl.reuseTLSSecret | Reuse existing TLS Secret during chart upgrade | <code>false</code> |
| webhook.ssl.ca.cert | For outbound connections (secure backend, proxy,...) <br/>And inbound connections to serve HttpRequests as Kubernetes Webhook. <br/>A PEM-encoded x509 certificate authority. <br/>If empty, a new CA will be autogenerated. | <code>""</code> |
| webhook.ssl.ca.key | For outbound connections (secure backend, proxy,...) <br/>A PEM-encoded private key of the certificate authority to use in the certificate generation. <br/>If empty, a new CA will be autogenerated. | <code>""</code> |
| webhook.ssl.cert | For inbound connections to serve HttpRequests as Kubernetes Webhook. <br/>A PEM-encoded x509 certificate signed by the CA. <br/>If empty, a new cert will be generated. <br/>If provided, it must be valid with the `webhook.ssl.ca`. <br/>If this is set, the key must also be provided. | <code>""</code> |
| webhook.ssl.key | For inbound connections to serve HttpRequests as Kubernetes Webhook. <br/>A PEM-encoded private key signed by the CA. <br/>If empty, a new key will be generated. <br/>If provided, it must be valid with the `webhook.ssl.ca`. <br/>If this is set, the cert must also be provided. | <code>""</code> |
| webhook.ssl.ca.cert | For outbound connections (secure backend, proxy,...) <br/>A PEM-encoded x509 certificate authority. | <code>""</code> |
| webhook.customEntryPoint | Custom entrypoint for the webhook <br/>Remember to provide the webhook valid arguments with `--tls_cert_file` and `--tls_private_key_file`. <br/>default: /bin/webhook --tls_cert_file /cert/tls.crt --tls_private_key_file /cert/tls.key | <code>[]</code> |
| webhook.http.port | HTTP serve port where the requests will be served from | <code>5000</code> |
| scc.create | Enable the creation of Security Context Constraints in Openshift | <code>true</code> |
Expand Down Expand Up @@ -176,15 +173,15 @@ The following table lists the configurable parameters of the `admission-controll
| scanner.priorityClassName | priorityClassName config for the scanner | <code></code> |
| scanner.tolerations | Tolerations for scheduling for the scanner | <code>[]</code> |
| scanner.affinity | Configure affinity rules for the scanner | <code>{}</code> |
| scanner.ssl.ca.cert | For outbound connections (secure backend, proxy,...). <br/>A PEM-encoded x509 certificate authority. <br/>If empty, a new CA will be autogenerated. | <code>""</code> |
| scanner.ssl.ca.cert | For outbound connections (secure backend, proxy,...). <br/>A PEM-encoded x509 certificate authority. | <code>""</code> |
| scanner.customEntryPoint | Custom entrypoint for the scanner. <br/>Remember to provide the scanner valid arguments with `--server_port` and optionally `--auth_secure_token` <br/>default: /inline-scan-service --server_port=8080 | <code>[]</code> |


Specify each parameter using the **`--set key=value[,key=value]`** argument to `helm upgrade --install`. For example:

```console
$ helm upgrade --install sysdig-admission-controller sysdig/admission-controller \
--create-namespace -n sysdig-admission-controller --version=0.11.4 \
--create-namespace -n sysdig-admission-controller --version=0.11.5 \
--set sysdig.secureAPIToken=YOUR-KEY-HERE,clusterName=YOUR-CLUSTER-NAME
```

Expand All @@ -193,7 +190,7 @@ installing the chart. For example:

```console
$ helm upgrade --install sysdig-admission-controller sysdig/admission-controller \
--create-namespace -n sysdig-admission-controller --version=0.11.4 \
--create-namespace -n sysdig-admission-controller --version=0.11.5 \
--values values.yaml
```

Expand Down
19 changes: 0 additions & 19 deletions charts/admission-controller/values.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -220,26 +220,8 @@ webhook:
reuseTLSSecret: false
ca:
# For outbound connections (secure backend, proxy,...)
# <br/>And inbound connections to serve HttpRequests as Kubernetes Webhook.
# <br/>A PEM-encoded x509 certificate authority.
# <br/>If empty, a new CA will be autogenerated.
cert: ""
# For outbound connections (secure backend, proxy,...)
# <br/>A PEM-encoded private key of the certificate authority to use in the certificate generation.
# <br/>If empty, a new CA will be autogenerated.
key: ""
# For inbound connections to serve HttpRequests as Kubernetes Webhook.
# <br/>A PEM-encoded x509 certificate signed by the CA.
# <br/>If empty, a new cert will be generated.
# <br/>If provided, it must be valid with the `webhook.ssl.ca`.
# <br/>If this is set, the key must also be provided.
cert: ""
# For inbound connections to serve HttpRequests as Kubernetes Webhook.
# <br/>A PEM-encoded private key signed by the CA.
# <br/>If empty, a new key will be generated.
# <br/>If provided, it must be valid with the `webhook.ssl.ca`.
# <br/>If this is set, the cert must also be provided.
key: ""

# Custom entrypoint for the webhook
# <br/>Remember to provide the webhook valid arguments with `--tls_cert_file` and `--tls_private_key_file`.
Expand Down Expand Up @@ -348,7 +330,6 @@ scanner:
ca:
# For outbound connections (secure backend, proxy,...).
# <br/>A PEM-encoded x509 certificate authority.
# <br/>If empty, a new CA will be autogenerated.
cert: ""

# Custom entrypoint for the scanner.
Expand Down

0 comments on commit 209c438

Please sign in to comment.