You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks the removal of fallback to IMDS v1 endpoints and the introduction of retry logic for IMDS v2 in oci-python-sdk
IMDS (Instance Metadata Service) endpoints provide region information and metadata for Instance Principal, Resource Principal, and etc. To ensure the security and functionality of this feature, IMDS v1 fallback will be removed from all SDKs. After this change, if the IMDS v2 endpoint is unavailable, there will be no fallback to IMDS v1. Applications relying on v1 fallback must update accordingly to avoid service disruptions.
Changes Implemented
Remove Fallback to IMDS v1:
The SDK will no longer attempt to access IMDS v1 if IMDS v2 requests fail.
Retry Mechanism for IMDS v2 in Auth:
A retry strategy has been introduced with 8 retry attempts and exponential backoff with Jitter between attempts
This change will take effect starting from the version 2.141.0
The text was updated successfully, but these errors were encountered:
This issue tracks the removal of fallback to IMDS v1 endpoints and the introduction of retry logic for IMDS v2 in oci-python-sdk
IMDS (Instance Metadata Service) endpoints provide region information and metadata for Instance Principal, Resource Principal, and etc. To ensure the security and functionality of this feature, IMDS v1 fallback will be removed from all SDKs. After this change, if the IMDS v2 endpoint is unavailable, there will be no fallback to IMDS v1. Applications relying on v1 fallback must update accordingly to avoid service disruptions.
Changes Implemented
Remove Fallback to IMDS v1:
The SDK will no longer attempt to access IMDS v1 if IMDS v2 requests fail.
Retry Mechanism for IMDS v2 in Auth:
A retry strategy has been introduced with 8 retry attempts and exponential backoff with Jitter between attempts
This change will take effect starting from the version
2.141.0
The text was updated successfully, but these errors were encountered: