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
Next create a values file. To avoid confusen i recomend you name this file the same as your namespace and the "instance" you are creating. So imaging you want to deploy an openflow instance responding to demo.mydomain.com then create a file names demo.yaml
21
+
Next create a values file. To avoid confusen i recomend you name this file the same as your namespace and the "instance" you are creating. So imaging you want to deploy an openflow instance responding to demo.mydomain.com then create a file named demo.yaml
22
22
23
-
There is a ton of different settings you can fine tune, you can always find all the settings in the openflow [values file here](https://github.com/open-rpa/helm-charts/blob/main/charts/openflow/values.yaml) but you only need to add the values you want to override, so get you started this would be a good starting point to add to your demo.yaml file
23
+
There is a ton of different settings you can fine tune, you can always find all the settings in the openflow [values file here](https://github.com/open-rpa/helm-charts/blob/main/charts/openflow/values.yaml) but you only need to add the values you want to override. So as a good starting point, add the following to your demo.yaml file
24
24
25
25
```yaml
26
26
# this will be the root domain name hence your openflow url will now be http://demo.mydomain.com
@@ -43,7 +43,7 @@ So first we need to create a namespace. Namespaces allow us to segregate multipl
43
43
```sh
44
44
kubectl create namespace demo
45
45
```
46
-
and now we can create our first openflow installation
46
+
and now we can create our first openflow installation inside that namespace
0 commit comments