20240512 Updates

The following changes have been applied to reflect the for removal or update in the documentation:

• Remove Deprecated Deployment Instructions:

  • Any references to deployment practices that no longer apply, especially if the deployment process has been streamlined or changed significantly. For example, if the process for deploying to dev and qa environments has been automated or changed, the relevant sections should be updated or removed.

• Update Container Registry References:

  • If the VRO no longer uses GHCR (GitHub Container Registry) as its primary container registry, or if there have been changes in how images are stored, tagged, or managed, these references need to be updated accordingly.

• Revise Environment Policies:

  • The policy details regarding signed and unsigned images for different environments (dev, qa, sandbox, prod-test, and prod) might need revision. If the policies on image signing have changed, the documentation should reflect the current requirements.

• Update Partner Team Deployment Guide:

  • If the steps for partner teams to deploy and verify feature branch changes independently have changed, or if the guide now covers code releases or deployments to higher environments, this section should be updated to reflect the current process.

• Reflect Changes in VRO Architecture or Design Principles:

  • Any significant changes in the VRO architecture, such as moving away from Kubernetes clusters hosted on AWS or changes in the design principles underlying VRO, should be accurately represented in the documentation.

• Reflect Changes in Tools, Services, or Support Team Information:

  • If there have been updates or changes to the tools, services, or support team information provided by the Lighthouse Delivery Infrastructure (LHDI) platform, these should be updated in the documentation.

Based on the notes provided, here is a bulleted list of markdown changes that need to be considered for removal or update:

• Remove outdated deployment instructions that no longer apply to the current deployment process.
• Update all references to container registries if there have been changes to the storage, tagging, or management of Docker images.
• Revise the sections detailing environment-specific policies for signed and unsigned images to reflect current security practices.
• Update the Partner Team Quick Deployment Guide to reflect the current steps for deployment and verification in dev and qa environments, including any new provisions for higher environments.
• Amend the VRO Architecture Diagram and descriptions if there have been changes in the infrastructure or design principles.
• Update the LHDI's Boilerplate Instructions to reflect the current state of tools, services, and support available to VRO and its partner teams.

These changes should ensure that the markdown documentation accurately reflects the current state and practices of the VRO system.