10000 Kemp LoadMaster under Load Balancer by dishanktiwari2501 · Pull Request #8867 · chef/automate · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Kemp LoadMaster under Load Balancer #8867

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

dishanktiwari2501
Copy link
Collaborator

🔩 Description: What code changed, and why?

The current Chef Automate HA documentation does not reference Kemp LoadMaster as a preferred load balancer. 

Business Rationale: 
In alignment with our strategic priority to support cross-sell opportunities within the Progress portfolio, we are updating the documentation to include Progress Kemp LoadMaster as a preferred external load balancer for Chef Automate HA deployments.  

Required documentation updates are required: 

HA Prerequisites Page 

Update the “External Supported Software” section to include Kemp LoadMaster as a preferred load balancer.  Kemp loadmaster would be the first one and highlighted as (Preferred)

Provide Load Master Product link  

⛓️ Related Resources

https://progresssoftware.atlassian.net/browse/CHEF-20848

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

With occasional exceptions, all PRs from Progress employees must tick these:

  • Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
  • Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
  • Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
  • Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
  • Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

  • Tests added/updated? (all new code needs new tests)
  • Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
@dishanktiwari2501 dishanktiwari2501 added the documentation Anything related to the Automate docs. label Apr 17, 2025
@dishanktiwari2501 dishanktiwari2501 self-assigned this Apr 17, 2025
@dishanktiwari2501 dishanktiwari2501 requested a review from a team as a code owner April 17, 2025 11:08
Copy link
netlify bot commented Apr 17, 2025

Deploy Preview for chef-automate ready!

< 8000 thead>
Name Link
🔨 Latest commit d88ad59
🔍 Latest deploy log https://app.netlify.com/projects/chef-automate/deploys/6840039f06ea740008397583
😎 Deploy Preview https://deploy-preview-8867--chef-automate.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
Signed-off-by: Dishank Tiwari <dtiwari@progress.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Anything related to the Automate docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0