You should load the rule base separately based on Pega documentation. For example, if the database is postgresql, you should follow this link to complete rule base loaded (ignore app server configuration part, that is equivalent to helm chart):
It seems to do nothing. It says 'mypega' was created and that's it. I have not used Helm before but I assumed it would actually execute the action I have defined in the pega.yaml. I have created a pod for postgresql in my minikube environment and was going to actually install pega into that instance (which has a mounted permanent volume). Is there another command which is required?
Also, I am on Windows 10. Docker installation enables Hyper-V but my Minikube uses Virtual Box. I have to toggle Hyper-V enablement to do what I need with Docker and then minikube. I think I can switch Minikube to use Hyper-V instead of Virtual Box but for now have been doing brute force. Question @KevinZheng_GCS once I get the above helm command to do the install/deploy to minikube will the image pull from the docker repository I configure need docker daemon to be running on my local host? If so then I would need to fix the issue I just described with Hyper-V as I can only have minikube or docker running at the moment.
The pega.yaml does not populate the real values as you may have noticed. Assuming you have loaded your rulebase traditionally (you can also use pega-installer image, which now you can download directly).
The only file you need to edit is the values.yaml, use minimal version for your local env, which has Search.Stream,Backgroundprocessing,WebUser configured. If you want to run Pega Marketing you would need to specify the following node types (ADM,RTDG,RealTime,Batch,Search,Stream,Backgroundprocessing,WebUser,Custom1,Custom2)
---see an example of my values.yaml without passwords