first PR to migrate pybot to K8s

dmarchante commented 3 years ago

TODO:

Ingress.yaml needs to updated and verifed for values
Docker Image ref => get value
Get info for ALB
Obtain values for channels
DNS/Ext DNS? => update slack U Ito use new values, if necessary
Identify how BE and pybot interact => DNS
Application for ArgoCD
Verify Pybot ports and health endpoints

Need secret values:

apiVersion: v1
data:
SLACK_BOT_SIGNING_SECRET: ...
BOT_USER_OAUTH_ACCESS_TOKEN: ...
AIRTABLE_API_KEY: ...
AIRTABLE_BASE_KEY: ...
kind: Secret
metadata:
name: pybot-secrets
namespace: operationcode-staging
type: Opaque

Teardown old pybot

irvingpop commented 3 years ago

For DNS, by adding the host definitions to the Ingress, the external-dns k8s add-on will automatically create the records in the k8s.operationcode.org domain in Route53 ( https://console.aws.amazon.com/route53/v2/hostedzones#ListRecordSets/Z2QGEWMWUT7EEB )

irvingpop commented 3 years ago

We can ignore the validate failures - the TF code just needs to be ripped out soon

dmarchante commented 3 years ago

Note to self: I still need to make the secrets file.

aaron-junot commented 2 years ago

We can probably close this in favor of @JudsonStevens' rewrite https://github.com/OperationCode/operationcode-pybot/tree/judson/rewrite

OperationCode / operationcode_infra

first PR to migrate pybot to K8s #176