Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S seismic-dms-service
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Domain Data Management Services
  • Seismic
  • Seismic DMS Suite
  • seismic-dms-service
  • Merge requests
  • !288

fix: Azure MSI timeout error

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Dmitriy Rudko requested to merge fix/rudkodm/msi-timeout-error into Azure/OSDU-Seismic-DDMS-M8-Master Dec 14, 2021
  • Overview 9
  • Commits 6
  • Pipelines 10
  • Changes 10

This PR provides two separate fixes for the MSI issue on Azure:

  1. The latency for the MSI endpoint call could be longer than 500ms. The first fix wrap default Azure credentials object and:
    • Increase call timeout to 5 sec
    • Implements retry logic
  2. The second fix is focused on cases wen POD has been provisioned on the K8S node that still doesn't have MSI assigned. Usually, this can happen either at initial provisioning or during auto-scaling of the application. In this case, we do handle this on K8S level using readiness probe.
Edited Dec 16, 2021 by Sacha Brants
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix/rudkodm/msi-timeout-error