k8s-redis-ha | Kubernetes Redis with High Availability | Crawler library

by tarosky Shell Version: 3.0.1 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | k8s-redis-ha Summary

k8s-redis-ha is a Shell library typically used in Automation, Crawler applications. k8s-redis-ha has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Kubernetes Redis with High Availability

Support

Quality

Security

License

Reuse

Support

k8s-redis-ha has a low active ecosystem.

It has 129 star(s) with 69 fork(s). There are 12 watchers for this library.

It had no major release in the last 12 months.

There are 7 open issues and 9 have been closed. On average issues are closed in 12 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of k8s-redis-ha is 3.0.1

Quality

k8s-redis-ha has no bugs reported.

Security

k8s-redis-ha has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

k8s-redis-ha is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

k8s-redis-ha releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of k8s-redis-ha

Get all kandi verified functions for this library.

k8s-redis-ha Key Features

No Key Features are available at this moment for k8s-redis-ha.

k8s-redis-ha Examples and Code Snippets

No Code Snippets are available at this moment for k8s-redis-ha.

Community Discussions

Trending Discussions on k8s-redis-ha

Kubernetes init containers run every hour

QUESTION

Kubernetes init containers run every hour

Asked 2018-Aug-20 at 03:32

I have recently set up redis via https://github.com/tarosky/k8s-redis-ha, this repo includes an init container, and I have included an extra init container in order to get passwords etc set up.

I am seeing some strange (and it seems undocumented) behavior, whereby the init containers run as expected before the redis container starts, however then they run subsequently every hour, close to an hour. I have tested this behavior using a busybox init container (which does nothing) on deployments & statefulset and experience the same behavior, so it is not specific to this redis pod.

I have tested this on bare metal with k8s 1.6 and 1.8 with the same results, however when applying init containers to GKE (k8s 1.7) this behavior does not happen. I can't see any flags for GKE's kubelet to dictate this behavior.

See below for kubectl describe pod showing that the init containers are run when the main pod has not exited/crashed.

...

ANSWER

Answered 2018-Aug-19 at 20:46

If you are pruning away exited containers, then the container pruning/removal is a likely cause. In my testing, it appears that exited init containers which are removed from Docker Engine (hourly, or otherwise), such as with "docker system prune -f" will cause Kubernetes to re-launch the init containers. Is this the issue in your case, if this is still persisting?

Also, see https://kubernetes.io/docs/concepts/cluster-administration/kubelet-garbage-collection/ for Kubelet garbage collection documentation, which appears to support these types of tasks (rather than needing to implement it yourself)

Source https://stackoverflow.com/questions/49247931

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install k8s-redis-ha

If you already have a Kubernetes cluster, you can deploy High Availability Redis using the following command:.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: