cloud-automation
cloud-automation copied to clipboard
uc-cdis
Automation for standing up Gen3 commons
update to latest EKS + AMI + CNI + t3 node type * [https://github.com/aws/amazon-vpc-cni-k8s/releases](https://github.com/aws/amazon-vpc-cni-k8s/releases) * [https://github.com/awslabs/amazon-eks-ami/issues/27](https://github.com/awslabs/amazon-eks-ami/issues/27) * [https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html) * [https://docs.aws.amazon.com/eks/latest/userguide/platform-versions.html](https://docs.aws.amazon.com/eks/latest/userguide/platform-versions.html) * [https://www.zdnet.com/article/kubernetes-first-major-security-hole-discovered/](https://www.zdnet.com/article/kubernetes-first-major-security-hole-discovered/) * [https://aws.amazon.com/ec2/instance-types/](https://aws.amazon.com/ec2/instance-types/)
@phillis @Fauzi - I'm going to look into extending our reverse proxy to support canary deployments of new code: • setup `-canary` services that point at `-canary` deployments - configured...
Similar to peregrine: * [https://github.com/uc-cdis/cloud-automation/blob/master/kube/services/peregrine/peregrine-deploy.yaml](https://github.com/uc-cdis/cloud-automation/blob/master/kube/services/peregrine/peregrine-deploy.yaml) * [https://github.com/uc-cdis/cloud-automation/tree/master/Docker/sidecar](https://github.com/uc-cdis/cloud-automation/tree/master/Docker/sidecar) * [https://github.com/uc-cdis/peregrine/blob/master/dockerrun.sh](https://github.com/uc-cdis/peregrine/blob/master/dockerrun.sh) Note that fence currently uses Apache internally, thank to its support for a SAML client for dbgap authentication, but most of...
reset the databases for every test suite run ... see if we can get that to work ...
extend `gen3` and `cdis-manifest` to support deploying helm charts: * specify chart version in manifest instead of docker image * specify template overrides in gitops * setup help chart repository...
Sit down with Fauzi, Zac, and Zakir - decide how we want jupyterhub to be deployed going forward
we would like to have a monitoring dashboard to see the container resource usage as the first step. in the future, we would like to monitor: * VM's disk, cpu,...
Setup logic in the `cdis-jenkins-lib` to support jenkins pipelines for `gen3-qa` and `gitops-*` PR's
Sean recommends that we look into using `curator` (I don't know about it) to automate the index rotation in our logs elastic search cluster.
