Skip to content

Commit 6475f81

Browse files
operator, ns, cr, crd
1 parent 74c3942 commit 6475f81

File tree

2 files changed

+54
-19
lines changed

2 files changed

+54
-19
lines changed

content/operate/kubernetes/architecture/_index.md

Lines changed: 54 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -11,22 +11,57 @@ linkTitle: Architecture
1111
weight: 1
1212
---
1313

14-
Redis Enterprise gives you redis's speed at scale with added durability.
15-
Kubernetes (K8s) is flexible, scalable, and automates management while reducing overhead. Redis Enterprise for Kubernetes lets you manage your Redis clusters and databases with declarative configuration files, and lets you use the advantages of Kubernetes to manage your resources. Redis Enterprise for Kubernetes uses a custom operator and custom controllers to bring the best of Redis Enterprise to Kubernetes platforms.
16-
17-
Redis Enterprise for Kubernetes provides custom resource definitions (CRDs) that allows you to to create custom resources to manage your clusters and databases. The RedisEnterpriseCluster (REC) resource creates and manages a Redis Enterprise cluster within the same namespace. The RedisEnterpriseDatabase (REDB) resource creates and manages your Redis Enterprise database.
18-
19-
overview diagram
20-
21-
Declarative configuration management... configuration YAML files - https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/
22-
Automated upgrades, creation, scaling, declare state you want and K8s manages details
23-
where is my database ... just like RS multiple databases are hosted by a redis node, just happens to be within a pod
24-
db diagram
25-
Once its up, it's just RS except...
26-
Credentials management - secrets
27-
Storage - k8s way - network attached
28-
Active-active
29-
multi-namespace
30-
flexible deployment
31-
more information?
32-
https://redis.io/redis-enterprise/advantages/
14+
Redis Enterprise for Kubernetes gives you the speed and durability of [Redis Enterprise](https://redis.io/redis-enterprise/advantages/), along with the flexibility and ease of use Kubernetes (K8s) provides. Redis Enterprise for Kubernetes uses a custom operator and custom controllers to bring the best of Redis Enterprise to Kubernetes platforms.
15+
16+
The image below illustrates the components of a single-namespace deployment.
17+
18+
{{< image filename="/images/k8s/k8s-arch-v4.png" >}}
19+
20+
## Operator
21+
22+
An operator is a custom extension of the Kubernetes API used to manage complex, stateful processes and resources. The operator uses controllers to manage Redis Enterprise's custom resources (CR).
23+
24+
## Namespace
25+
26+
The Redis Enterprise operator is deployed into a namespace. Only one operator and one RedisEnterpriseCluster can reside in each namespace. Namespaces create a logical separation between resources. Several of the resources used in your deployment are limited to a namespace, while others are cluster-wide.
27+
28+
Redis Enterprise for Kubernetes supports multi-namespace deployment options. Databases residing in one namespace, can be monitored and managed by an operator.
29+
30+
## Custom resources
31+
32+
Custom resources extend the Kubernetes API to allow Redis users to manage their databases the Kubernetes way. Custom resources are created and managed with YAML configuration files.
33+
34+
This [declarative configuration method](https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/) lets you define a desired state for your resources, and the operator will make changes to reach that state. This simplifies installing, updating, and scaling (both horizontally and vertically).
35+
36+
The operator continually monitors custom resources for changes, and acts to reconcile differences between your declared desired state and the actual state of your resources.
37+
38+
## Custom resource definitions
39+
40+
A cluster-wide resource called a custom resource defintion (CRD) specifies which settings are configurable via a custom resource configuration file. Any setting not defined by the CRD is not managed by the operator. Changes to these settings can be made just as they are in Redis Enterprise Software.
41+
42+
Settings that are managed by the operator will be overwritten if changed by a method besides the custom resource YAML files. Be aware that changes made in the management UI will be overwritten by the operator if that setting is defined by the CRD.
43+
44+
## RedisEnterpriseCluster REC
45+
46+
## RedisEnterpriseDatabase REDB
47+
48+
{{< image filename="/images/k8s/k8s-node-arch.png">}}
49+
50+
## Active-Active databases
51+
52+
### RedisEnterpriseRemoteCluster RERC
53+
54+
### RedisEnterpriseActiveActiveDatabase REAADB
55+
56+
## Services Rigger
57+
58+
## Security
59+
60+
secrets
61+
62+
## Storage
63+
64+
PVCs, network attached
65+
66+
## Metrics
67+

static/images/k8s/k8s-arch-v4.png

-13.8 KB
Loading

0 commit comments

Comments
 (0)