Allow IAM authentication to communal storage #265
Merged
Conversation
This file contains 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
This relaxes things in the operator so that the communal credential secret isn't required. Prior to this, the credential secret was required if connecting to a s3://, azb://, or gs:// endpoint. This will allow us to authenticate with IAM when connecting on AWS. AWS provides two methods of authenticating with IAM: - EC2 IAM authentication: an IAM role is attached to the EC2 instance. All pods running on the EC2 instance will be able to use the attached roles. - IAM roles for service accounts: this is for more fine-grained access control. You can use this to attach IAM roles to a ServiceAccount. All pods running with the ServiceAccount will be able to use the roles. This feature requires a Vertica service of at least 12.0.3 (not yet available at the time of this PR). You will need to specify an existing ServiceAccount in the helm chart when deploying the operator. More details will be included in the official Vertica documentation once a server with support is GA'd.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This relaxes things in the operator so that the communal credential secret isn't required. Prior to this, the credential secret was required if connecting to a s3://, azb://, or gs:// endpoint.
This will allow us to authenticate with IAM when connecting on AWS. AWS provides two methods of authenticating with IAM: