Skip to content

refactor(juno): Sunset Assets server #643

Description

@edda

Plan retirement of assets server:

  • Elektra MFEs
  • Resourcemanagement
  • Emailservice

Standalone apps:

  • Global dashboard (Landing page)
    • migrate to Elektra repo and include as widget
    • change standalone deployment to pull asset from Elektra
  • Volta
  • Whois
  • Andromeda (Andy)
  • scale pods count in qa to 0
  • scale pods count in prod to 0
  • delete all helm installations in qa and prod
  • cleanup ci folder, leave only hosting pipeline
  • cleanup other folders
  • cleanup docker images in keppel (check that no pulls are happening until the end of the week)
    • juno base image
    • juno asset-server
    • juno ci-helper
  • create new cc-landing-page pipeline
    • move hosting pipeline to cc-landing-page in secrets ci
    • move landing page deployment from juno namespace (scalout) into elektra
    • link ccloud.global.cloud.sap and converged-cloud.global.cloud.sap to the load balancer in new deployed regions
  • cleanup old dns entries
    • assets.juno.global.cloud.sap/ (eu-nl-1)
    • exampleapp.juno.global.cloud.sap (eu-nl-1)
    • assets.juno.qa-de-1.cloud.sap
    • assets.qa-de-1.cloud.sap
    • exampleapp.juno.qa-de-1.cloud.sap
    • ui.juno.qa-de-1.cloud.sap
    • assets.juno.eu-nl-1.cloud.sap.
    • exampleapp.juno.eu-nl-1.cloud.sap.
    • ui.juno.eu-nl-1.cloud.sap.
  • move e2e folder to cc-landing-page (secrets ci) and adjust the pipeline to load them from there
  • remove ci and e2e folder from legacy juno repo
  • migrate swift shared tasks into elektra pipeline

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions