https://deploy-preview-206--kured.netlify.app/docs/Recent content in kured - Kubernetes Reboot Daemon onHugo -- gohugo.ioenhttps://deploy-preview-206--kured.netlify.app/docs/installation/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/installation/Default installation with manifests To obtain a default installation without Prometheus alerting interlock or Slack notifications: latest=$(curl -s https://api.github.com/repos/kubereboot/kured/releases | jq -r '.[0].tag_name') kubectl apply -f "https://github.com/kubereboot/kured/releases/download/$latest/kured-$latest-combined.yaml" If you want to customise the installation, download the manifest and edit it in accordance with the following section before application. Using the Helm-Chart Kured also provides its own helm-chart. Detailed instructions and documentation can be found here. Kubernetes & OS Compatibility The daemon image contains versions of k8s.https://deploy-preview-206--kured.netlify.app/docs/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/configuration/The following arguments can be passed to kured via the daemonset pod template: Kubernetes Reboot Daemon Usage: kured [flags] Flags: --alert-filter-regexp regexp.Regexp alert names to ignore when checking for active alerts --alert-filter-match-only Only block if the alert-filter-regexp matches active alerts --alert-firing-only only consider firing alerts when checking for active alerts --annotate-nodes if set, the annotations 'weave.works/kured-reboot-in-progress' and 'weave.works/kured-most-recent-reboot-needed' will be given to nodes undergoing kured reboots --blocking-pod-selector stringArray label selector identifying pods whose presence should prevent reboots --drain-delay duration delay drain for this duration (default: 0, disabled) --drain-grace-period int time in seconds given to each pod to terminate gracefully, if negative, the default value specified in the pod will be used (default -1) --drain-pod-selector string only drain pods with labels matching the selector (default: '', all pods) --drain-timeout duration timeout after which the drain is aborted (default: 0, infinite time) --ds-name string name of daemonset on which to place lock (default "kured") --ds-namespace string namespace containing daemonset on which to place lock (default "kube-system") --end-time string schedule reboot only before this time of day (default "23:59:59") --force-reboot force a reboot even if the drain fails or times out -h, --help help for kured --lock-annotation string annotation in which to record locking node (default "weave.https://deploy-preview-206--kured.netlify.app/docs/operation/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/operation/The example commands in this section assume that you have not overriden the default lock annotation, daemonset name or namespace; if you have, you will have to adjust the commands accordingly. Testing You can test your configuration by provoking a reboot on a node: sudo touch /var/run/reboot-required Disabling Reboots If you need to temporarily stop kured from rebooting any nodes, you can take the lock manually: kubectl -n kube-system annotate ds kured weave.https://deploy-preview-206--kured.netlify.app/docs/building/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/building/Kured now uses Go Modules, so build instructions vary depending on where you have checked out the repository: Building outside $GOPATH: make Building inside $GOPATH: GO111MODULE=on make You can find the current preferred version of Golang in the go.mod file. If you are interested in contributing code to kured, please take a look at our development docs.https://deploy-preview-206--kured.netlify.app/docs/faq/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/faq/Why is there no latest tag on Docker Hub? Use of latest for production deployments is bad practice - see here for details. The manifest on main refers to latest for local development testing with minikube only; for production use choose a versioned manifest from the release page. Make kured run on control-plane with taint In a cluster setup your control-plane might have taints that block the kured deployment. To get the taints of your cluster node you can run the following commands:https://deploy-preview-206--kured.netlify.app/docs/community/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/community/Getting Help If you have any questions about, feedback for or problems with kured: Invite yourself to the CNCF Slack and ask a question on the #kured slack channel. File an issue. You might want to join the kured-dev mailing list as well. We follow the CNCF Code of Conduct. Your feedback is always welcome! Next Meeting Meetings are currently on hold, as we do not need synchronous meetings at the moment.https://deploy-preview-206--kured.netlify.app/docs/development/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-206--kured.netlify.app/docs/development/We love contributions to kured, no matter if you are helping out on Slack, reporting or triaging issues or contributing code to kured. In any case, it will make sense to familiarise yourself with the main documentation to understand the different features and options, which is helpful for testing. The “building” section in particular makes sense if you are planning to contribute code. Prepare your environment Your IDE The core team has access to Goland from JetBrains.