## Use Case <!-- Describe the use case and problem set this feature will solve. --> Allow orchestrator users to deploy with SSL enabled using a certificate they already have on hand. ## Scope of Work <!-- Define how broadly this use case applies and how it impacts customers --> SSL is the defacto standard. ## Contextual Information <!-- - Why is this work being requested? - What is the priority and severity of this request? e.g ~P3 ~S3 - What is the impact to project consumers and stakeholders? - Are there any known risks that may require mitigation during planning or implementation? --> Work is requested to maintain security standards. ## Acceptance Criteria <!-- How do we measure success and consider the work complete? --> User provided SSL certificates will be injected to the deployment allowing `https://gitlab.example.com` to work. <!-- Labels here --> <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->