...
Release Name - "natours-"+FD_ENVIRONMENT_CODE.toLowerCase()
Chart Path - https://github.com/joel-wenzel/charts/raw/develop/generic-0.1.0.tgz
This chart will create a single pod deployment with a load balancer service.
Helm Parameters
These will likely change depending on your chart and docker image.
...
Deploying the Helm Release
Head back to the Project Activity Screen and click the deploy button. If everything goes well there will be a new successful deployment of the Helm Release.
...
You may notice a few things that stand out compared to other FlexDeploy Projects, namely the Deployment link and Status. Both of these are shown for Container Projects only and offer some insight into the actual application that was deployed and some basic monitoring.
| Info |
|---|
The deployment status is only monitored if Kubectl is installed on the local FlexDeploy server. |
Bonus: Image Scanning
If you have made it this far you have seen the bread and butter of Kubernetes deployments in FlexDeploy. If you want to take things to the next level this section will incorporate Image scanning via Anchore in our build process.
FlexDeploy supports native Anchore inline image scanning. What this means for you is that no additional installations or setup is needed apart from updating the Project configuration.
| Warning |
|---|
At this time, inline(local) image scanning is not supported on windows |
Updating the Project Image Scanning Configuration
Navigate back to the Container Configuration tab on the Project. Under the Image Scanning section, change the Scan Image drop down to Before Push and set the Fail When script to
STATUS == “fail”.
...
We have just told FlexDeploy to run an Anchore scan prior to pushing our image and if the scan Status is “fail” then the build will fail. Save the changes and run another build. If you are using the natours repository, the build will now fail due to the scan results.
...