Skip to content

Broken kubernetes deployment, expired kubeconfig

Created by: Tirokk

roschaefer Authored by roschaefer Closed

Describe the bug Our deployment has stopped working and is failing every single master build now. Screenshot (59)

To Reproduce This is a hard-to-reproduce bug and I believe this happens after a week or two when you downloaded the kubeconfig from Digital Ocean for the first time.

Expected behavior Travis CI should reliably deploy every commit on master which is passing the build. I believe we have to do more research how to do continuous deployment with kubernetes on our build server.

Screenshots Screenshot (60)

Installing deploy dependencies
dpl.2
Preparing deploy
Cleaning up git repository with `git stash --all`. If you need build artifacts for deployment, set `deploy.skip_cleanup: true`. See https://docs.travis-ci.com/user/deployment#Uploading-Files-and-skip_cleanup.
Saved working directory and index state WIP on (no branch): aea25be Merge pull request #333 from Human-Connection/dependabot/npm_and_yarn/webapp/graphql-14.2.1
dpl.3
Deploying application
error: You must be logged in to the server (Unauthorized)
error: You must be logged in to the server (Unauthorized)
Already up to date!
HEAD detached at aea25be
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)
	modified:   scripts/patch-deployment.yaml
Untracked files:
  (use "git add <file>..." to include in what will be committed)
	send.sh
	tester.sh
no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (5b2568f994e499288dd2bcbe74d552d6d94843ce)
Script failed with status 1
failed to deploy