8
8
- [ Prerequisites] ( #prerequisites )
9
9
- [ Testing templates] ( #testing-templates )
10
10
- [ Deploying charts] ( #deploying-charts )
11
+ - [ Github as Helm Chart Repository] ( #github-as-helm-chart-repository )
11
12
4 . [ Additional Information] ( #additional-information )
12
13
- [ Trigger scanning] ( #trigger-scanning )
13
14
- [ Connect to database using Azure Data Studio] ( #connect-to-database-using-azure-data-studio )
@@ -49,7 +50,7 @@ curl https://raw.githubusercontent.com/zricethezav/gitleaks/master/config/gitlea
49
50
Create two folders in your user folder and name them _ database_ and _ rabbitmq_ as described below.
50
51
51
52
Windows: C:\Users\< username>\resc\database and C:\Users\< username>\resc\rabbitmq
52
- Linux: /Users/<username >/var/resc/database and /Users/<username >/var/resc/rabbitmq
53
+ Linux: /Users/<username >/var/resc/database and /Users/<username >/var/resc/rabbitmq
53
54
54
55
Update persistent volume claim path and hostOS for database.
55
56
```
@@ -92,8 +93,8 @@ Below is an example for how to scan repositories from GitHub.
92
93
For example, let's say you want to scan all the repositories for the following GitHub accounts.
93
94
https://github.com/kubernetes
94
95
https://github.com/docker
95
-
96
- Then you need to add those accounts to scope like : [ "kubernetes", "docker"] . All the repositories from those accounts will be scanned.
96
+
97
+ Then you need to add those accounts to scope like : [ "kubernetes", "docker"] . All the repositories from those accounts will be scanned.
97
98
* exceptions (optional): If you want to exclude any account from scan, then add it to exceptions. Default is empty exception.
98
99
* usernameValue: Provide your GitHub username.
99
100
* tokenValue: Provide your GitHub personal access token if you wish to scan private repositories.
@@ -134,10 +135,10 @@ Render chart templates locally and display the output.
134
135
helm template resc . -f ./example-values.yaml --set-file global.secretScanRulePackConfig=./RESC-RULE.toml
135
136
```
136
137
137
- ## Deploying charts
138
+ ## Deploying charts
138
139
Make sure you have completed the [ pre-requisite] ( #prerequisites ) steps.
139
140
140
- * Ensure the namespace is created, if not then run
141
+ * Ensure the namespace is created, if not then run
141
142
``` bash
142
143
kubectl create namespace resc
143
144
```
@@ -146,11 +147,11 @@ Make sure you have completed the [pre-requisite](#prerequisites) steps.
146
147
cd ./deployment/kubernetes/
147
148
```
148
149
149
- * Deploy the helm charts.
150
+ * Deploy the helm charts.
150
151
``` bash
151
152
helm install --namespace resc resc . -f ./example-values.yaml --set-file global.secretScanRulePackConfig=./RESC-RULE.toml
152
153
```
153
-
154
+
154
155
* Optionally, set the default namespace for all kubectl commands. Now you no longer need to specify the -n resc option for all the kubectl commands.
155
156
``` bash
156
157
kubectl config set-context --current --namespace=resc
@@ -172,6 +173,12 @@ Make sure you have completed the [pre-requisite](#prerequisites) steps.
172
173
helm uninstall resc --namespace resc
173
174
```
174
175
176
+ ### GitHub as Helm Chart Repository
177
+ It is now possible to directly download the files from the Repository Scanner (RESC) GitHub Repository since it now also
178
+ acts as a helm repository! This helm repository allows for a quicker and easier way to obtain the helm charts and use them
179
+ on your machine. For a full step-by-step approach on how to install the helm charts, visit the README on the "gh-pages" branch
180
+ linked [ here] ( https://github.com/abnamro/repository-scanner/blob/gh-pages/README.md ) .
181
+
175
182
## Additional Information
176
183
### Issue while pulling images?
177
184
If any image is not getting pulled automatically from the registry, you can use ` docker pull ` command to pull that image manually.
0 commit comments