You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+38-1Lines changed: 38 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ For now the ProxyInjector only supports [Keycloak Gatekeeper](https://github.com
25
25
The following quickstart let's you set up ProxyInjector:
26
26
27
27
1. Add configuration to the ProxyInjector
28
-
The following arguments can either be added to the proxy injector `config.yaml` in the ConfigMap for centralized configuration,
28
+
The following arguments can either be added to the proxy injector `config.yaml` in the ConfigMap/Secret for centralized configuration,
29
29
or as annotations on the individual target deployments with a `authproxy.stakater.com/` prefix. In case of both,
30
30
the deployment annotation values will override the central configuration.
31
31
@@ -40,6 +40,8 @@ The following quickstart let's you set up ProxyInjector:
40
40
41
41
The rest of the available options can be found at the [Keycloak Gatekeeper documentation](https://www.keycloak.org/docs/latest/securing_apps/index.html#configuration-options)
42
42
43
+
Note 1: See the section `Using Secrets` below if you do not want to use ConfigMap (because `client-id` and `client-secret` in plain text) and want to use Secrets to hide them.
44
+
43
45
2. Deploy the controller by running the following command:
44
46
45
47
For Kubernetes Cluster using kubectl
@@ -58,6 +60,41 @@ The rest of the available options can be found at the [Keycloak Gatekeeper docum
58
60
The `authproxy.stakater.com/listen` annotation or the `listen` property in the ProxyInjector ConfigMap should
59
61
specify where the proxy sidecar will listen for incoming requests, e.g. "0.0.0.0:80" i.e. local port 80
60
62
63
+
64
+
### Using Secrets
65
+
66
+
To use secrets:
67
+
68
+
1. Open [values.yaml](https://github.com/stakater/ProxyInjector/blob/master/deployments/kubernetes/chart/proxyinjector/values.yaml) file by navigating to `deployments/kubernetes/chart/proxyinjector/`
69
+
70
+
2. Set `mount` equals to `"secret"` and pass the data in the data section at the bottom.
71
+
72
+
3. Run `helm template .> proxyinjector.yaml`
73
+
74
+
4. Deploy using the `Deploying` section below.
75
+
76
+
### Using ConfigMap
77
+
78
+
To pass user credentials/ API keys in secrets:
79
+
80
+
1. Open [values.yaml](https://github.com/stakater/ProxyInjector/blob/master/deployments/kubernetes/chart/proxyinjector/values.yaml) file by navigating to `deployments/kubernetes/chart/proxyinjector/`
81
+
82
+
2. Set `mount` equals to `"configmap"` and pass the data in the data section at the bottom.
83
+
84
+
3. Run `helm template .> proxyinjector.yaml`
85
+
86
+
4. Deploy using the `Deploying` section below.
87
+
88
+
### Deploying
89
+
90
+
You can deploy the controller in the namespace you want to monitor by running the following kubectl command:
*Note*: Before applying `proxyinjector.yaml`, You need to modify the namespace in the `RoleBinding` subjects section to the namespace you want to apply RBAC to.
0 commit comments