redis cluster kubernetes

Especially when creating pods, you will encounter all kinds of problems, please check the error details by the following command.Kubectl describe pod xxxxxx1. Problem phenomenon: Mirroring is always not getting downWORKAROUND: Set up a mirror source for Docker--registry-mirror=http://f2d6cb40.m.daocloud.io'2. Symptom: There is a certificate error in the error message, certificate xxxx, execute on node nodesYum Install *rhsm*-y3. Problem phenomenon: When using the Docker private library, when pro

[TOC] Redis Note-taking (ii): Java API use with Redis distributed cluster environment using Redis Java API (i): Standalone version of Redis API usageThe Redis Java API operates through Jedis, so the first Jedis third-party l

Redis cluster _ 3. redis master-slave automatic switch Sentinel, redis_3.redisRedis SentinelSentinel (Sentinel) is a tool used to monitor the Master Status in redis clusters. It has been integrated into redis2.4 + versions.I. Role of Sentinel:1): Master status detection2) If the Master node is abnormal, the Master-Slav

Kube-proxy Questions: Apr1209:42:Compute1 kube-proxy[12965]: E041209:42:49.60234212965 Reflector.go:205] Pkg/proxy/config/api.go:33: Failed to List *api. Endpoints:get http://109.105.46.94:8080/api/v1/endpoints?resourceversion=0:dial TCP 109.105.46.94:8080: getsockopt:connection refusedapr: $ compute1 kube-proxy[12965]: E0412 49.602373: 12965 reflector.go:205] Pkg/proxy/config/api.go: Failed tolist *api. Service:get http://109.105.46.94:8080/api/v1/services?resourceversion=0:dial TCP 109.

Tag:hostnameroles Mirror etcdmaster ber deployment hosttab Ip Hostname Roles 172.50.0.120 Kube-harbor Harbor Mirror Warehouse 172.50.0.110 Kube-master-01 172.50.0.111 kube-master-02 172.50.0.112 kube-master-03 172.50.0.116 Kube-node01 172.50.0.117 Kube-node02 172.50.0.118 Kube-node03

[email protected] ~]# Yum groupinstall-y "Development Tools"[Email protected] ~]# yum-y install Epel-release[Email protected] ~]# yum-y install python-dev* libevent-dev* python-pip* openssl-devel xz-devel libffi-dev*[[email protected] ~]# git clone https://github.com/docker/docker-registry.git[Email protected] ~]# CD docker-registry/[[email protected] docker-registry]# lsAdvanced.md changelog.md config contributing.md depends docker_registry faq.md manifest.in requirements Setu P.CFG TestsAUTHOR

also build a private warehouse, upload the pod-infrastructure:latest image to a private repository, and modify the address of this profile. Start the service:To view ports: Repeat the above operation on the NODE02 host. Check the node status on master:Five Building a private warehouse:Kubernetes Management Container If this is the first operation, there may be some waiting time, because the first download of images takes a while. If there is no Docker registry locally, make sure tha

Test the Cluster of Redis Cluster on Windows to fill in the note, redisclusterFor the principle of redis cluster implementation, see the http://www.tuicool.com/articles/VvIZje cluster environment requires at least three nodes. We

Tags: des art csdn get scribe run Master pre ASTUse Kubectl Run Nginx--image=nginx After viewing: Kubectl describe pods Found in creating state, and Error: (Unable to ping registry endpoint Https://gcr.io/v0/\nv2 Ping attempt failed with Error:get https://gcr.io/v2/: ... Cause: Gcr.io by the wall, unable to ping. Workaround: On each nodes, pull the relevant image from Dockerhub and hit the new tag: (You can use ansible to resolve) Docker pull docker.io/kuber