Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

kubernetes deploy once config is in place #3

Open
12 tasks
macrozone opened this issue Jul 12, 2017 · 0 comments
Open
12 tasks

kubernetes deploy once config is in place #3

macrozone opened this issue Jul 12, 2017 · 0 comments

Comments

@macrozone
Copy link
Member

we deploy our new apps to kubernetes on google cloud.

For this we need the following steps, once the config is there:

  • [ ]determine new <tag>
  • catladder build-server <env>
  • docker build -t <app-name-x>
  • docker tag <app-name-y> gcr.io/skynet-164509/<namespace>:<tag>
  • docker push gcr.io/skynet-164509/<namespace>:<tag>(needs auth)
  • OR (on my machine only this works: gcloud docker -- push gcr.io/skynet-164509/<namespace>:<tag>
  • change ./kube/<env>/deployment.<app-name>_web.yml and set to new<tag> (e.g. namespace:v30 to namespace:v31)
  • same for ./kube/<env>/deployment.<app-name>_worker.yml (if has worker)
  • kubectl apply -f ./kube/<env>/deployment.<app-name>_web.yml
  • kubectl apply -f ./kube/<env>/deployment.<app-name>_worker.yml (if has worker)

Need to know:

  • what is <app-name-x> ? it does not seem to be the . How it has to match to the config?
  • is gcr.io/skynet-164509 the same for all apps?
  • is <app-name-y> the exact same as <app-name-x> ?
@macrozone macrozone added this to backlog in kubernetes deploy Jul 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Development

No branches or pull requests

1 participant