Add hero.jpg

Signed-off-by: obaydullahmhs <[email protected]>

Author: obaydullahmhs

content/post/kubedb-v2024.06.04/hero.jpg

@@ -7,10 +7,10 @@ authors:
 tags:
 - alert
 - backup
+- clickhouse
 - cloud-native
 - dashboard
 - database
-- clickhouse
 - druid
 - grafana
 - kafka
@@ -115,7 +115,7 @@ spec:
   topology: {}
 ```
 
-### Ops Request
+### OpsRequest
 In this release, support for Druid Ops Request support has been integrated. Druid Ops Request provides a declarative configuration for the Druid administrative operations like database restart, vertical scaling, volume expansion, etc. in a Kubernetes native way.
 
 #### Restart
@@ -356,8 +356,50 @@ We have introduced support for Sharded MongoDB Cluster in the `mongodb-csi-snaps
 Specific components restoression provided in KubeStash Restoression wasn’t working properly. This bug has been fixed in this release.
 
 ## Memcached
+### Custom Configuration
+This release introduces custom configuration for Memcached. By using custom configuration file, you can use KubeDB to run Memcached with custom configuration.
+The necessary information required for custom configuration is memcached.conf file which is the Memcached configuration file containing the custom configurations. For custom configuration, you can use YAML like this:
+
+```yaml
+apiVersion: v1 
+stringData: 
+  memcached.conf: | 
+    -m 32
+    -c 500
+kind: Secret 
+metadata: 
+  name: mc-configuration 
+  namespace: demo 
+  resourceVersion: "4505"
+```
+
+In the above YAML, -m is max memory limit to use for object storage & -c is max simultaneous connections.
+
+To apply this custom configuration, the Memcached YAML will be like:
+```yaml
+apiVersion: kubedb.com/v1alpha2
+kind: Memcached
+metadata:
+  name: memcached
+  namespace: demo
+spec:
+  replicas: 1
+  version: "1.6.22"
+  configSecret:
+    name: mc-configuration
+  podTemplate:
+    spec:
+      resources:
+        limits:
+          cpu: 500m
+          memory: 128Mi
+        requests:
+          cpu: 250m
+          memory: 64Mi
+  terminationPolicy: WipeOut
+```
 
-### Ops Request
+### OpsRequest
 Memcached Ops Request support has been introduced through this release. Ops Request for Restart, Vertical Scaling, and Reconfiguration have been added.
 
 #### Restart
@@ -444,7 +486,7 @@ Previously there were multiple postgres database servers which the pgbouncer can
 Health check is configured in this release. Now it can do write check and it can check every pgbouncer pod if it is healthy or not.
 
 ## Pgpool
-### Ops Request
+### OpsRequest
 In this release, we have introduced support for Pgpool Ops Requests. Current Ops Request supports for Pgpool are: Restart, Vertical Scaling, and Reconfigure.
 #### Restart
 Restart ops request is used to perform a smart restart to Pgpool pods. An example YAML is provided below:
@@ -542,7 +584,7 @@ Alpine: https://github.com/kubedb/postgres-docker/tree/release-15.5-alpine-age
 Debian: https://github.com/kubedb/postgres-docker/tree/release-15.5-bookworm-age
 
 ## RabbitMQ
-### Ops Requests
+### OpsRequest
 
 This release is going to introduce more OpsRequest for RabbitMQ clusters. The last release included RabbitMQ OpsRequests for Restart, Vertical Scaling, and Volume Expansion. This release brings support for Horizontal Scaling, Update Version, Reconfigurations, and ReconfigureTLS. Here’s a sample YAML for Upgrading RabbitMQ v3.12.12 cluster named **rabbitmq** in demo namespace to v3.13.2 - 
 
@@ -613,7 +655,7 @@ spec:
 
 ## SingleStore
 
-### Ops Request
+### OpsRequest
 In this release, we have introduced support for SingleStore Ops Requests. Initially, Ops Requests for Restart, Vertical Scaling, Volume Expansion, and Reconfiguration have been added for both clustering and standalone modes.
 
 #### Vertical Scaling