Greg
f8d964f8d2
It was previously set to extensions/v1beta1. I have discovered that when the Deployment is created as a extensions/v1beta1, it causes the existing pod to be killed immediately when doing a rolling update. When the Deployment was created as apps/v1, a rolling update behaves as expected: a new pod is created, and the old one is only terminated once the new pod is ready to serve traffic. The existing Deployment resource will need to be deleted and recreated: kubectl delete deployment gitea-server kubectl apply -f gitea-server.yaml Applying the file without deleting it first will not fix the issue with rolling updates. It will cause a short downtime |
||
---|---|---|
custom/options/label | ||
doc | ||
kubernetes | ||
packer | ||
script | ||
.gitignore | ||
README.md |
README.md
gitea.kosmos.org
This repository contains configuration files and other assets, that are used to deploy and operate this Gitea instance.
To create a new image containing the customizations:
Edit packer/custom.json
to increment the tag, then run this script (needs
Packer in your path)
./script/build_customizations_image
Then edit kubernetes/gitea-server.yaml
to use the new tag
(image: eu.gcr.io/fluted-magpie-218106/gitea_custom:$VERSION
) and apply the
change:
cd kubernetes
kubectl apply -f gitea-server.yaml
Feel free to open issues for questions, suggestions, bugs, to-do items, and whatever else you want to discuss or resolve.