OperationCode / OperationCode/operationcode_infra

Bring all the projects into kubernetes

Open
#61 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HCL
Stars
17
Forks
12
PR merge metrics
No merged PRs in 30d

Description

This issue is to track bringing our current prod assets into kubernetes.
operationcode-pybot
operationcode-pyback
front-end

Currently the first 2 are hosted on ECS using ECR, with amazon RDS.
The third one is not hosted but we'd like to set it up to be able to point the staging frontend url to it in the very near future.

By doing it in this manner we are better able to track our assets and apply monitoring solutions to each in a standardized way which can help prevent re-inventing the wheel.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how operationcode-pybot and operationcode-pyback are currently hosted on ECS using ECR and Amazon RDS, then assess the unhosted front-end. Done should mean all three projects run in Kubernetes with standardized monitoring, including a staging frontend URL.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.