https://fortinetcloudcse.github.io/faig-training-workshop/02_fortiaigate_setup/index.htmlFortiAIGate Installation In the previous sections we worked on getting an environment to run Kubernetes (K8s), installing K8s, and setting up additional containers and pods to build out the resources we will protect in this demo environment. The next step will be to install FortiAIGate itself using the supplied helm charts that come with the FortiAIGate release files. Background Information FortiAIGate is distributed via a collection of container files in tar (Tape ARchive) format that must be loaded into a container repository so that they are available for download by K8s when deployed. We have already completed this step for you, but a customer might need to setup their own repo server (for example the Harbor repository server) and upload the images there. The FortiAIGate values.yaml file would need to be updated to reflect that new repo server location.Hugoen-UShttps://fortinetcloudcse.github.io/faig-training-workshop/02_fortiaigate_setup/01_troubleshoot_postgresql_startup.htmlMon, 01 Jan 0001 00:00:00 +0000https://fortinetcloudcse.github.io/faig-training-workshop/02_fortiaigate_setup/01_troubleshoot_postgresql_startup.htmlWhen to Use This Page Use this procedure when a new FortiAIGate installation remains unhealthy and api, core, or logd reports: P1000: Authentication failed against database server at `fortiaigate-postgresql` New Workshop Installations Only This recovery deletes the failed FortiAIGate installation and its stored data. Use it only for a new workshop installation with no data to preserve. A P1000 message by itself is not enough to identify this incident.