Skip to content
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

Add Option to Deploy NGINX for Load Balancing in Helm Chart #120

Closed
jsbroks opened this issue Apr 23, 2024 · 0 comments · Fixed by #128
Closed

Add Option to Deploy NGINX for Load Balancing in Helm Chart #120

jsbroks opened this issue Apr 23, 2024 · 0 comments · Fixed by #128
Assignees

Comments

@jsbroks
Copy link
Member

jsbroks commented Apr 23, 2024

Objective:

Provide an option within our Helm chart to deploy NGINX as a load balancer, catering to customers who may not have an existing ingress controller configured in their Kubernetes clusters. This should enhance the flexibility and usability of our deployments, especially for environments lacking this infrastructure.

Details:

  • Integrate a subchart within our main Helm chart that specifically handles the deployment and configuration of NGINX as a load balancer.
  • Ensure that this NGINX load balancer can be easily enabled or disabled based on user preference. This allows users to either use the provided NGINX setup or their existing ingress solutions without conflicts.
  • The NGINX load balancer should be pre-configured to manage traffic routing effectively, adhering to best practices and ensuring optimal performance and reliability.
  • Update our documentation to include instructions on how to enable/disable this feature, configuration options, and scenarios where this might be preferable to using a standard ingress controller.
@jsbroks jsbroks linked a pull request Apr 23, 2024 that will close this issue
@jsbroks jsbroks removed their assignment May 14, 2024
@amanpruthi amanpruthi linked a pull request May 30, 2024 that will close this issue
@amanpruthi amanpruthi removed a link to a pull request May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants