vsphere: add support for per-component vCenter credentials#10313
Draft
rvanderp3 wants to merge 1 commit intoopenshift:mainfrom
Draft
vsphere: add support for per-component vCenter credentials#10313rvanderp3 wants to merge 1 commit intoopenshift:mainfrom
rvanderp3 wants to merge 1 commit intoopenshift:mainfrom
Conversation
Adds ComponentCredentials field to VCenter type to allow specifying separate credentials for each OpenShift component (machine-api, CSI driver, cloud controller, diagnostics). This enables least-privilege security by allowing different vCenter accounts with minimal permissions for each component. The installer can now: - Load component credentials from ~/.vsphere/credentials file (INI format) - Fall back to main VCenter username/password if not specified - Generate separate credential secrets for each component - Validate credential file permissions (must be 0600) Components affected: - machine-api-operator - vSphere CSI driver - Cloud controller manager - vsphere-problem-detector
openshift-ci
bot
added
the
do-not-merge/work-in-progress
Contributor
|
Skipping CI for Draft Pull Request. |
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
Author
|
/test ? |
Contributor
|
@rvanderp3: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds ComponentCredentials field to VCenter type to allow specifying separate credentials for each OpenShift component (machine-api, CSI driver, cloud controller, diagnostics). This enables least-privilege security by allowing different vCenter accounts with minimal permissions for each component.
The installer can now:
Components affected: