I'm attempting to deploy ArcGIS Enterprise for Kubernetes but I am having some issues with the ./deploy.sh script when it attempts to deploy the ingress controller. Here are a few background details:
After entering in the details for the script and executing it, it appears to run fine until it reaches the ingress controller part, at which point it provides the following error before rolling back:writing new private key to '/home/mobaxterm/.install/resources/tmp/ingress-controller.keyfile.key.587.tmp'
-----
error: Cannot read file /home/mobaxterm/.install/resources/tmp/ingress-controller.certificate.crt.587.tmp, open /home/mobaxterm/.install/resources/tmp/ingress-controller.certificate.crt.587.tmp: The system ca nnot find the path specified.
ERROR: Command failed: Run kubectl create secret tls arcgis-interpod-cert-pem --cert="/home/mobaxterm/.install/resources/tmp/ingress-controller.certificate.crt.587.tmp" --key="/home/mobaxterm/.install/r esources/tmp/ingress-controller.keyfile.key.587.tmp" -n arcgis
(Attachment is an example of this).
As far as I can tell, these files are created as part of the installation process and ARE found in the location in which the script is claiming it cannot be found, so I'm not sure what is going on there. I'm thinking it might have something to do with MobaXterm and the folder paths, and will be looking into using a Linux box as my next test (though my Linux command game is not very strong at all)
Has anyone else had issues similar to this when attempting to install?
Thanks.
Solved! Go to Solution.
We've seen a few issues when using bash emulators as opposed to a native bash shell, so using a native bash shell on Linux is recommended for the deployment scripts. Since it seems to be having issues with the certificate portion in particular, you may be able to get around it by creating a TLS secret in the namespace yourself and specifying it in the deployment script (option 1 in the SSL settings prompt).
https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets
We've seen a few issues when using bash emulators as opposed to a native bash shell, so using a native bash shell on Linux is recommended for the deployment scripts. Since it seems to be having issues with the certificate portion in particular, you may be able to get around it by creating a TLS secret in the namespace yourself and specifying it in the deployment script (option 1 in the SSL settings prompt).
https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets
Using a native bash shell resolved this issue. After spinning up a Ubuntu EC2 configuring it with the required pre-reqs (AWS CLI and kubectl) I was able to successfully run the deployment script on the first try.
Thanks!