Bug 1293399 - [RFE] Certificate Tool: Modify
Summary: [RFE] Certificate Tool: Modify
Keywords:
Status: CLOSED DUPLICATE of bug 1293395
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Mike Barrett
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1293395
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-21 16:49 UTC by Eric Jones
Modified: 2023-09-14 03:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
OpenShift Enterprise 3.1
Last Closed: 2016-04-14 20:14:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Jones 2015-12-21 16:49:33 UTC
- What is the nature and description of the request?  
As an admin I need the ability to add or remove certificates and certificate authorities from my .kube/config so that I can take advantage of using multiple CAs, including private ones.

- Why does the customer need this? (List the business requirements here)  
So that they can add to the CA they are using. This could come up if you add a Load Balancer that is using a different CA from the rest of your environment. This is already a case with a customer.

- How would the customer like to achieve this? (List the functional requirements here)  
Add an oc or kube command that can modify the CAs, certificates,and keys listed in the .kube/config on each node/master.
The ability to Modify, or add to/remove from, the current features. 

- Is there already an existing RFE upstream or in Red Hat Bugzilla?  
Not that I could find  

- List any affected packages or components.  
OpenShift
Kubernetes

Comment 3 Dan McPherson 2016-04-14 20:14:15 UTC

*** This bug has been marked as a duplicate of bug 1293395 ***

Comment 4 Red Hat Bugzilla 2023-09-14 03:15:14 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.