kubernetes-statefulset | 易学教程

How to extract volumeClaimTemplates to a separate PersistentVolumeClaim yaml file?

阅读更多关于 How to extract volumeClaimTemplates to a separate PersistentVolumeClaim yaml file?

问题 Let's say I have a StatefulSet definition apiVersion: v1 kind: StatefulSet metadata: name: web spec: ... volumeClaimTemplates: — metadata: name: www spec: resources: requests: storage: 1Gi This will create me a PersistentVolumeClaim (PVC) with a PersistentVolume (PV) of 1 GiB for each pod. How can I write something like this apiVersion: v1 kind: PersistentVolumeClaim metadata: name: www spec: ... resources: requests: storage: 1Gi ... and connect it with the StatefulSet in a way that it still

apply HPA for Statefulset in kubernetes?

阅读更多关于 apply HPA for Statefulset in kubernetes?

问题 I am trying to setup HPA for my statefulset(for elasticsearch) in kubernetes environment. I am planning to scale the statefulset using the cpu utilization. I have created the metric server from https://github.com/stefanprodan/k8s-prom-hpa/tree/master/metrics-server. and my HPA yaml for statefulset is as folows: apiVersion: autoscaling/v2beta1 kind: HorizontalPodAutoscaler metadata: name: dz-es-cluster spec: scaleTargetRef: apiVersion: extensions/v1beta1 kind: StatefulSet name: dz-es-cluster

Redis Pods are not able to join Redis cluster

阅读更多关于 Redis Pods are not able to join Redis cluster

问题 I want to create redis cluster of 6 nodes in kubernetes. I am running kubernetes using Minikube . Below is my implementation for creating the 6 node cluster. kind: StatefulSet metadata: generation: 1 labels: app: demo-app name: demo-app namespace: default spec: podManagementPolicy: OrderedReady replicas: 6 revisionHistoryLimit: 10 selector: matchLabels: app: demo-app serviceName: "" template: metadata: creationTimestamp: null labels: app: demo-app spec: containers: - command: - redis-server -

Kubernetes service architecture

阅读更多关于 Kubernetes service architecture

问题 Within the same kubernetes cluster, Can I have multiple StatefulSets attached to one headless service or should each StatefulSet have it's own headless service? What are the pros and cons of doing this? Can I mix standard and headless services in the same cluster? Specifically, I would like to use LoadBalancer service to load balance headless services. Can I define a service of type LoadBalancer and have headless services (ClusterIP = None) attached to it? If yes, how can I achieve this? Here

Kubernetes StatefulSet - obtain spec.replicas metadata and reference elsewhere in configuration

阅读更多关于 Kubernetes StatefulSet - obtain spec.replicas metadata and reference elsewhere in configuration

问题 I am configuring a StatefulSet where I want the number of replicas ( spec.replicas as shown below) available to somehow pass as a parameter into the application instance. My application needs spec.replicas to determine the numer of replicas so it knows what rows to load from a MySQL table. I don't want to hard-code the number of replicas in both spec.replicas and the application parameter as that will not work when scaling the number of replicas up or down, since the application parameter

Why StatefulSets? Can't a stateless Pod use persistent volumes?

阅读更多关于 Why StatefulSets? Can't a stateless Pod use persistent volumes?

问题 I am trying to understand Stateful Sets. How does their use differ from the use of "stateless" Pods with Persistent Volumes? That is, assuming that a "normal" Pod may lay claim to persistent storage, what obvious thing am I missing that requires this new construct (with ordered start/stop and so on)? 回答1: Yes, a regular pod can use a persistent volume. However, sometimes you have multiple pods that logically form a "group". Examples of this would be database replicas, ZooKeeper hosts, Kafka

Why StatefulSets? Can't a stateless Pod use persistent volumes?

阅读更多关于 Why StatefulSets? Can't a stateless Pod use persistent volumes?

I am trying to understand Stateful Sets . How does their use differ from the use of "stateless" Pods with Persistent Volumes? That is, assuming that a "normal" Pod may lay claim to persistent storage, what obvious thing am I missing that requires this new construct (with ordered start/stop and so on)? Yes, a regular pod can use a persistent volume. However, sometimes you have multiple pods that logically form a "group". Examples of this would be database replicas, ZooKeeper hosts, Kafka nodes, etc. In all of these cases there's a bunch of servers and they work together and talk to each other.