Conversation
|
If we're planning to do a release using this gen3-helm PR, can we move the Kafka work to another branch? If I recall correctly, the Kafka work was a proof of concept anyways. |
Testing Steps (Creating Local K8s Cluster):1. Start Docker Desktop ✅➜ open -a Docker2. Create Kind Cluster ✅kind-config.yamlkind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: kind-multi-node
networking:
ipFamily: ipv4
apiServerAddress: 127.0.0.1
nodes:
- role: control-plane
kubeadmConfigPatches:
- |
kind: InitConfiguration
nodeRegistration:
kubeletExtraArgs:
node-labels: "ingress-ready=true"
extraPortMappings:
- containerPort: 80
hostPort: 80
protocol: TCP
- containerPort: 443
hostPort: 443
protocol: TCPkind create cluster --config kind-config.yaml3. Create Ingress NGINX Controller ✅4. Update
|
|
Note Thanks @matthewpeterkort for unblocking the local SSL issue that allowed the local testing to continue! Caution Only a basic "Hello, World!" file was tested for upload and download (no rich metadata) Warning These steps were run with OHSU's fork of gen3-client to avoid the the mismatch issue between a file's uploaded path and it's GUID in Indexd Overview
Testing Steps (Gecko + GRIP/GRIDS)1. Update Secrets ✅➜ scp -r <cbds-prod>:/cbds/gen3-helm/Secrets ./Secrets-local
➜ ln -s Secrets-local Secrets
# Enable Gecko Service
➜ echo "gecko:\n enabled: true" >> Secrets/values.yaml2. Update Dependencies ✅➜ gh pr checkout 78
branch 'feature/grip-updates' set up to track 'origin/feature/grip-updates'.
Switched to a new branch 'feature/grip-updates'
➜ helm dependency build helm/gen3
➜ make update3. Deploy ✅➜ make local
Switched to context "kind-kind-multi-node".
Deploying local
...
NAMESPACE: default
STATUS: deployed
REVISION: 14. Verify
|
Adds gecko service for config wrangling. See https://github.com/ACED-IDP/gecko
Swaps mongo driver for grip grids driver, thus removing mongodb service.
Re configures ETL routing from /graphql to /writer so that /graphql can be used for grip graphql reader
nginx.ingress.kubernetes.io/proxy-body-size: 10240mneeds to be added to ingress to allow for larger body sizes.
this should be added to the annotations section with
kubectl edit ingress revproxy-dev -n default