Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a kubernetes cluster for GCP (first iteration) #1

Closed
7 tasks done
ThomasCardin opened this issue Dec 15, 2023 · 1 comment · Fixed by #4
Closed
7 tasks done

Create a kubernetes cluster for GCP (first iteration) #1

ThomasCardin opened this issue Dec 15, 2023 · 1 comment · Fixed by #4
Assignees
Labels

Comments

@ThomasCardin
Copy link
Member

ThomasCardin commented Dec 15, 2023

This should also include:

  • Step 1: Create a GKE cluster using terraform.
  • Step 2: Deploy the ingress nginx
  • Step 3: Deploy cert-manager
  • Step 4: Deploy a sample application the see if cert-manager is working fine.
  • Step 5: Deploy Hashicorp vault to manage secrets
  • Step 6: Deploy nachet-backend
  • Step 7: Deploy finesse-backend

For more information. Check the ADR at ai-cfia/dev-rel-docs#86

@ThomasCardin ThomasCardin self-assigned this Dec 15, 2023
@ThomasCardin ThomasCardin linked a pull request Dec 22, 2023 that will close this issue
@ThomasCardin ThomasCardin changed the title Create a kubernetes cluster for GCP w/ the ingress-nginx Create a kubernetes cluster for GCP (first iteration) Jan 5, 2024
ThomasCardin added a commit that referenced this issue Jan 17, 2024
ThomasCardin added a commit that referenced this issue Jan 17, 2024
ThomasCardin added a commit that referenced this issue Jan 17, 2024
ThomasCardin added a commit that referenced this issue Jan 31, 2024
ThomasCardin added a commit that referenced this issue Jan 31, 2024
ThomasCardin added a commit that referenced this issue Feb 7, 2024
* issue #1: GKE cluster using Terraform

* issue #1: Added vault to manage secrets

* issue #1: removed aws and azure provider it doesnt belong to this issue

* issue #1: removed unused cluster node pool

* issue #1: nachet-backend kubernetes deployment

* issue #1: added namespace to sa inside nachet deployment + finesse deployment

* increse proxy-read-timeout to 30m

* issue #1: kube-prometheus-stack (Prometheus, grafana and alertmanager)

* issue #1: Nachet deployment, with backend and frontend

* issue #1: updated the nachet backend image

* issue #1: fixed both ingress name for nachet

* issue #1: finesse frontend and backend deployed with our images from GCR

* issue #1: reviewed and added EOF on files

* issue #1: added new version to finesse-frontend

* issue #1: added github workflow

* issue #1: adding the workflow to the right folder

* issue #1: fixed md max line length

* issue #1: testing the workflow repo standard with applied patch

* issue #1: removed testing branch for repo standard action

* issue #1: testing the repo standard with new token

* issue #1: testing the repo standard with new token

* issue #1: EOF for workflow

* issue #1: fixed 413 error from frontend to backend

* issue #1: changed nachet images tag for PR number

* issue #1: changed README.md content

* issue #1: removed unused code

* issue #1: changed image version for finesse (default is main representing the develop branch)

* issue #1: changed default version of nachet-frontend

* deleted the GKE cluster

* added providers for the GKE cluster. Note: the cluster isn't supported anymore

* issue #1: fixed yaml linting error for nginx deployment

* issue #1: fixed yaml linting error for nginx deployment

* issue #1: fixed yaml linting error for nginx deployment

* issue #1: fixed some yaml linting error
@rngadam
Copy link

rngadam commented Feb 7, 2024

@ThomasCardin the issue is marked as completed but the list is incomplete.

If the last 3 remaining tasks are postponed, modify the checklist to provide pointers to the new issue to indicate the work has been postponed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants