Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-3012

Remove unused "Release Nexus" from AKS

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      As discussed with Olivier Vernin during the AKS 1.19 upgrade, the service "nexus-release" should be removed because:

      • It was a proof of concept while working on the "staging" of releases, and it was not retained as a solution
      • It is consuming resources (PVC included) for nothing in AKS
      • It is adding more elements on each Kubernetes migration

        Attachments

          Activity

          Hide
          dduportal Damien Duportal added a comment -

          Exchange with Aditya:

          • This operation will be a 2 steps process:
            • First step can be done in total autonomy: it consists in opening a Pull Request in https://github.com/jenkins-infra/charts to remove the helmfile release for nexus. Aditya you can do this in total autonomy until the PR is opened
            • Then, if the PR is merged (that should be the case) after review, then we'll wait 1-2 days to validate that it breaks nothing (it should keep the production resource, but stop updating it)
            • If everything is going without issues, then a pairing session with a member of team, with Aditya, will happen. The team member having access to the Kubernetes production, will have to delete the helm release associated to the service, so the resources would be deleted safely in production
          Show
          dduportal Damien Duportal added a comment - Exchange with Aditya : This operation will be a 2 steps process: First step can be done in total autonomy: it consists in opening a Pull Request in https://github.com/jenkins-infra/charts to remove the helmfile release for nexus. Aditya you can do this in total autonomy until the PR is opened Then, if the PR is merged (that should be the case) after review, then we'll wait 1-2 days to validate that it breaks nothing (it should keep the production resource, but stop updating it) If everything is going without issues, then a pairing session with a member of team, with Aditya , will happen. The team member having access to the Kubernetes production, will have to delete the helm release associated to the service, so the resources would be deleted safely in production
          Hide
          dduportal Damien Duportal added a comment -

          TODO for team members: we'll have to delete the nexus secret file in charts-secrets (as it is a private repository not reachable by Aditya)

          Show
          dduportal Damien Duportal added a comment - TODO for team members: we'll have to delete the nexus secret file in charts-secrets (as it is a private repository not reachable by Aditya )
          Hide
          kuro Aditya added a comment -

          Thank you Damien Duportal for your help. I have created the [pull request|https://github.com/jenkins-infra/charts/pull/1280.] Please let me know if there are some changes to be made.

          Show
          kuro Aditya added a comment - Thank you Damien Duportal  for your help. I have created the [pull request| https://github.com/jenkins-infra/charts/pull/1280 .] Please let me know if there are some changes to be made.
          Hide
          dduportal Damien Duportal added a comment -

          It was merged and deployed. Thanks a lot!

          Show
          dduportal Damien Duportal added a comment - It was merged and deployed. Thanks a lot!

            People

            Assignee:
            kuro Aditya
            Reporter:
            dduportal Damien Duportal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: