-
Notifications
You must be signed in to change notification settings - Fork 157
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
Deprecate CredentialTypeKeyPair #1310
Comments
Per triage meeting, this task will require documentation updated and deprecation announcement to the community. We will also need to document and optionally, provide some tools to users to help with upgrade. |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
🚀 |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
This issue is closed due to inactivity. Feel free to reopen it, if it's still relevant. |
We should deprecate the use of
CredentialTypeKeyPair
and switch to usingCredentialTypeSecret
for all types of Profiles.The key pair was useful when we supported only S3/S3 Compliant Profiles with the
AccessKeyID
andSecretAccessKey
combination. With the addition of IAM roles and other types of credentials, we have switched to using a K8s secret. This should be made the default for all Profiles.The text was updated successfully, but these errors were encountered: