fiaas / skipper Goto Github PK

The CustomResourceDefinition resource is out of beta in Kubernetes 1.16. apiextensions.k8s.io/v1beta1 CustomResourceDefinition, which FIAAS currently uses, will be removed in Kubernetes v1.22.

There are some changes that are necessary to transition FIAAS from using to apiextensions.k8s.io/v1 CustomResourceDefinition; we need to determine exactly what these are, and how to implement the changes in FIAAS.

Related to fiaas/fiaas-deploy-daemon#38. skipper can also create customresourcedefinitions for Application and ApplicationStatus, and must also be updated similarly to fiaas-deploy-daemon.

This repo use travis-ci.org for CI. travis-ci.org is planned for shutdown at the end of this month: https://blog.travis-ci.com/2021-05-07-orgshutdown
Since most of the other repos use SemaphoreCI, maybe it makes sense to move CI for this repo there too.

To be compatible with the BoundServiceAccountTokenVolume feature in Kubernetes 1.21 and later, skipper should re-read its service account token from disk every ~1 minute. See fiaas/k8s#98 for more details. Support for this is implemented in fiaas/k8s#104. See also this PR fiaas/fiaas-deploy-daemon#166 which takes the new feature in fiaas/k8s into use there.

If/when docker buildx gets some more documentation/stability, it would be beneficial to change to using it. Right now is not that time, but maybe later.

See #93 and the use-buildx branch to see what has been tried.

There seems to be an issue with the table showing currently running instances of fiaas-deploy-daemon in the status view in skipper. The table doesn't show fiaas-deploy-daemon instances in any namespaces, and there is an error in the browser console

Uncaught SyntaxError: JSON.parse: unexpected character at line 1 column 2 of the JSON data
    parseJSON jQuery
    success http://localhost:5001/static/skipper.js:21
    jQuery 6
    getStatus http://localhost:5001/static/skipper.js:17
    onStatusPageLoad http://localhost:5001/static/skipper.js:68
    <anonymous> http://localhost:5001/static/skipper.js:87
    jQuery 8
jquery.min.js:4:16646

This view is used to deploy fiaas-deploy-daemon in specific namespaces, which means that is no longer possible to do via the web UI. It should still be possible to deploy in specific namespaces via the API, or to all namespaces via the deploy view.

while draining a node containing skipper we found that it did not respond to the termination signal from kubernetes. It stayed in terminating state for the length of the grace period. There were also no logs while this was happening. Skipper should react to the termination signal in a graceful manner.

Currently we provide a way to create a simplified configmap for fiaas-deploy-daemon when installing Skipper.

This should be extended, so that users can install Skipper and fully configure fiaas-deploy-daemon at the same time if they wish. It should still be possible to skip creation of the fiaas-deploy-daemon configmap if the user has a different mechanism for doing this.