UCLA LIBRARY-CENTER FOR ORAL HISTORY RESEARCH --Documenting the histories of Los Angeles-- The UCLA Library creates a vibrant nexus of ideas, collections, expertise, and spaces in which users illuminate solutions for local and global challenges. We constantly evolve to advance UCLA’s research, education, and public service mission by empowering and
Estimate of 12 total hours to create helm charts for ucla oh’s blacklight application, including 2 hours to create documentation and 2 hours for pairing with the client to integrate with Argo CD and their applications micro services.
Currently the client is using existing shared postgres, and a stand alone, un-shared Solr VM that we will need to connect the deployment to.
Note: They would like to migrate over to a fully containerized approach and they have no chart preference to note.
When they are ready I would suggests that
They currently use HAProxy as a TLS endpoint, which handles the public-facing certificates.
Create helm charts for UCLA Oral History’s Blacklight application.
These charts will be used in deployments to a Rancher managed Kubernetes cluster through the continuous integration tool ArgoCD. We will be tapping into an existing, shared, Postgres database and a stand-alone Solr VM. We will be using vSphere CSI for the storageClass for the application’s PVCs. The secret strategy we will be using for this application is existing-secrets, and we will be using HAProxy as a TLS endpoint to handle the public-facing certificates for the site.
We will also be including basic helm chart documentation and how to use the helm chart’s values file in a dev workflow.
Provide 2 hours of pairing time to help staff integrate helm charts with pre-existing infrastructure.
Summary
Looking forward, UCLA Library will be decommissioning threir Docker Swarm environment and migrating all existing hosted applications to a Rancher managed Kubernetes cluster. They'll be using Argo CD with helm charts to manage the deployments.
Acceptance Criteria
[ ] Create Helm Charts for UCLA OH's Blacklight Application
[ ] Add default values for them to use in configuring to their needs.
[ ] Be available to the team for a 2 hour pairing block to help configure with exisiting microservices
[ ] Create basic helm chart documentation and outline how to use the values file in a dev workflow for deployments.
Estimate of 12 total hours to create helm charts for ucla oh’s blacklight application, including 2 hours to create documentation and 2 hours for pairing with the client to integrate with Argo CD and their applications micro services.
Currently the client is using existing shared postgres, and a stand alone, un-shared Solr VM that we will need to connect the deployment to.
They currently use HAProxy as a TLS endpoint, which handles the public-facing certificates.
The storage class we will be utilizing is vSphere CSI https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/3.0/vmware-vsphere-csp-getting-started/GUID-6DBD2645-FFCF-4076-80BE-AD44D7141521.html https://github.com/kubernetes-sigs/vsphere-csi-driver
UCLA OH’s secrets strategy is external secrets for this deployment setup. https://external-secrets.io/latest/
Convo in slack with John: https://assaydepot.slack.com/archives/C03UFN7017A/p1688587668010219
Scope:
Create helm charts for UCLA Oral History’s Blacklight application.
These charts will be used in deployments to a Rancher managed Kubernetes cluster through the continuous integration tool ArgoCD. We will be tapping into an existing, shared, Postgres database and a stand-alone Solr VM. We will be using vSphere CSI for the storageClass for the application’s PVCs. The secret strategy we will be using for this application is existing-secrets, and we will be using HAProxy as a TLS endpoint to handle the public-facing certificates for the site.
We will also be including basic helm chart documentation and how to use the helm chart’s values file in a dev workflow.
Provide 2 hours of pairing time to help staff integrate helm charts with pre-existing infrastructure.
Summary
Looking forward, UCLA Library will be decommissioning threir Docker Swarm environment and migrating all existing hosted applications to a Rancher managed Kubernetes cluster. They'll be using Argo CD with helm charts to manage the deployments.
Acceptance Criteria