-
Notifications
You must be signed in to change notification settings - Fork 66
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
Update Helm templates to account for lack of external load balancer support #623
Labels
impact/reliability
Something that feels unreliable or flaky
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
needs-triage
Needs attention from the triage team
size/M
Estimated effort to complete (up to 5 days).
Comments
scottslowe
added
impact/reliability
Something that feels unreliable or flaky
kind/enhancement
Improvements or new features
impact/usability
Something that impacts users' ability to use the product easily and intuitively
size/M
Estimated effort to complete (up to 5 days).
labels
Jul 28, 2023
Hi @scottslowe Minikube does support LoadBalancer. However, you may have to run the command
However, if the port number is set to 8080. You don't have to provide the password for sudo user else, in the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
impact/reliability
Something that feels unreliable or flaky
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
needs-triage
Needs attention from the triage team
size/M
Estimated effort to complete (up to 5 days).
The current Helm templates deploy the Nginx ingress controller and expose it with a Service of type LoadBalancer. This is fine for production-grade environments where the Kubernetes clusters have external load balancer support, but this can cause issues when testing the programs on platforms like KinD or Minikube. These platforms typically do not have external load balancer support.
Without external load balancer support, the Service never comes out of a pending state, and this causes Pulumi to report messages like this:
To fix this, we need to update the Helm templates in three ways:
Defaulting to a value of ClusterIP will help tests pass successfully, but are not conducive to actual production deployments. Defaulting to LoadBalancer is more in line with actual production deployments, but tests will fail if external load balancer support isn't present. The recommendation is to default to ClusterIP with comments in the code on how to change that for production deployments. Changes to the associated landing pages on the website may also be needed.
The text was updated successfully, but these errors were encountered: