-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy Fuel-Core Ingress with SSL Cert #209
Conversation
Have we tested a deployment of the latest iteration of this PR? |
Yes- I re-deployed the ingress controller, ingress, and cert-manager last night and it was a clean, successful deployment for https://node.swayswap.io https://github.com/FuelLabs/fuel-deployment/runs/5580179805?check_suite_focus=true I just need to write some documentation on it |
The following PR covers the configuration and deployment of:
This is adapted from open-source (https://github.com/kubernetes/ingress-nginx) for AWS EKS Network Load Balancer
Give its updated from open-source it will need to update per new releases of ingress-nginx in the fuel-core repo
This is straight forward install via helm chart and this can be easily update per new cert manager release - current version is v1.7.1
This is a ClusterIssuer k8s resource to issue a SSL certificate for the custom ingress dns domain - its customizable per env file
This is a custom k8s ingress resource that routes to the fuel-core NodePort backend service - its customizable per env file
This replaces the original k8s External Load Balancer and is a NodePort Service
Currently this is all deployed manually on the fuel-core EKS cluster, but the plan is to tear down the ingress controller and cert-manager one more and deploy via the fuel-deployment pipeline to verify all code changes.
Future work will be focused on updating the ingress-controller and ingress resource as needed.