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.

Sign up for GitHub

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

Jump to bottom

GUI HA : support for individul GUI node certificate #833

Open
Jainbrt opened this issue Nov 18, 2022 · 0 comments
Open

GUI HA : support for individul GUI node certificate #833

Jainbrt opened this issue Nov 18, 2022 · 0 comments
Assignees
@amdabhad
Labels
Customer Impact: Localized high impact (3) Reduction of function. Significant impact to workload. Customer Probability: Medium (3) Issue occurs in normal path but specific limited timing window, or other mitigating factor Found In: 2.7.0 For Bug issues to identify what release level issue was found in 2.7.0 Found In: 2.8.0 For Bug issues to identify what release level issue was found in 2.8.0 Found In: 2.9.0 For Bug issues to identify what release level issue was found in 2.9.0 Severity: 3 Indicates the the issue is on the priority list for next milestone. Type: Enhancement Indicates a request for feature to be improved.

Comments

@Jainbrt
Copy link
Member

Jainbrt commented Nov 18, 2022

Is your feature request related to a problem? Please describe.
GUI HA : support for individul GUI node certificate

Describe the solution you'd like
Today, GUI HA does support single certificate which should be same for all the GUI in the cluster, but customer may have different certificates for their GUI nodes. So we need to support individual node level certificate to be provided in CR spec

Describe alternatives you've considered
using common single certificate for all the GUI nodes is alternative today
@Jainbrt Jainbrt added Type: Enhancement Indicates a request for feature to be improved. Found In: 2.7.0 For Bug issues to identify what release level issue was found in 2.7.0 labels Nov 18, 2022
@Jainbrt Jainbrt added Customer Probability: Medium (3) Issue occurs in normal path but specific limited timing window, or other mitigating factor Customer Impact: Localized high impact (3) Reduction of function. Significant impact to workload. Severity: 3 Indicates the the issue is on the priority list for next milestone. Found In: 2.8.0 For Bug issues to identify what release level issue was found in 2.8.0 labels Nov 18, 2022
@Jainbrt Jainbrt added the Found In: 2.9.0 For Bug issues to identify what release level issue was found in 2.9.0 label Feb 1, 2023
@Jainbrt Jainbrt added this to the v2.9.0 milestone Feb 7, 2023
@Jainbrt Jainbrt modified the milestones: v2.9.0, v2.10.0 Mar 15, 2023
@deeghuge deeghuge removed this from the v2.10.0 milestone Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amdabhad amdabhad

Labels
Customer Impact: Localized high impact (3) Reduction of function. Significant impact to workload. Customer Probability: Medium (3) Issue occurs in normal path but specific limited timing window, or other mitigating factor Found In: 2.7.0 For Bug issues to identify what release level issue was found in 2.7.0 Found In: 2.8.0 For Bug issues to identify what release level issue was found in 2.8.0 Found In: 2.9.0 For Bug issues to identify what release level issue was found in 2.9.0 Severity: 3 Indicates the the issue is on the priority list for next milestone. Type: Enhancement Indicates a request for feature to be improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Jainbrt @deeghuge @amdabhad