Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4543

ArgoCD Repo Server stops pulling git repositories due to Azure Devops Repos current sunset SSH-RSA strategy

XMLWordPrintable

    • 8
    • False
    • None
    • False
    • Hide
      Before this fix, Argo CD would report errors when attempting to connect to Azure DevOps Repos, due to the Azure DevOps Repos service recently (May 2024) deprecating rsa-ssh host key algorithms using <= 256 bits in the signature. This fix ensures that Argo CD correctly reports support for these host key algorithms during the handshake process, allowing the pull from Azure DevOps Repos to succeed.
      Show
      Before this fix, Argo CD would report errors when attempting to connect to Azure DevOps Repos, due to the Azure DevOps Repos service recently (May 2024) deprecating rsa-ssh host key algorithms using <= 256 bits in the signature. This fix ensures that Argo CD correctly reports support for these host key algorithms during the handshake process, allowing the pull from Azure DevOps Repos to succeed.
    • Bug Fix
    • Done
    • GitOps Scarlet - Sprint 3257, GitOps Scarlet - Sprint 3256

      Description of problem:

      See upstream Argo CD issue for details: https://github.com/argoproj/argo-cd/issues/17634

      SSH RSA Deprecation notice
      https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/

      Steps to Reproduce

      As mentioned on the upstream issue, users of Azure Repos may encounter temporary failure when using Azure Repos with a non RSA-SHA2-256 or RSA-SHA2-512 key.

      This will become a permanent failure later in Q2 2024, when Azure Repos fully disables support for these deprecated ciphers.

       

       

              jgwest Jonathan West
              jgwest Jonathan West
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: