csye7125-fall2023-group05 / infra-helm-chart Goto Github PK

The consumer app root chart installs the consumer app from the Quay.io dockerhub, without validating/waiting for Postgres and Kafka charts to deploy their respective pods.

Do we need some initContainer logic here?

This helm chart will be used to deploy dependencies to our GKE cluster.
Install Kafka (& optionally Zookeeper). Use Bitnami's Kafka Helm chart to set up a highly reliable and available Kafka cluster.

Include Kiali as a dependency chart to visualize the istio service mesh and the components that are installed on the cluster, how they interact with each other, and see how the actual request flows through each application and istio envoy proxies, ingress and egress gateways.

Use the semantic-release/exec plugin to configure pushing tags to commits.

["@semantic-release/exec", {
    "prepareCmd": "git push --tags"
}]

User should be able to use git tag -l to list all tags for the current repository.

reference

• #9

• Use the quay.io/pwncorp/migrate:latest image as the initContainer image source instead of the busybox image which just performs no-op sleep of 80 seconds.
• Add DBSCHEMA for Flyway database migration to succeed (based on quay.io/pwncorp/migrate docker image for init containers)
• Update hardcoded configmap name to dynamic configmap name
• Update values.yaml to include postgresql v15.5 from bitnami

Use a distributed tracing tool like Jaeger or OpenTelemetry to configure distributed tracing in the GKE cluster, deployed as a dependency chart.

Kafka to be deployed in its own namespace. The consumer application and it's dependent postgresql database should be deployed in their own namespace.