# Storage-engine config cannot be changed (kubernetes)

**URL:** <https://discuss.aerospike.com/t/storage-engine-config-cannot-be-changed-kubernetes/9726>\
**Category:** Configuration\
**Created:** [September 9, 2022, 1:13am UTC](https://discuss.aerospike.com/t/storage-engine-config-cannot-be-changed-kubernetes/9726 "2022-09-09T01:13:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Khanh\_Nguyen](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/khanh_nguyen/32/1940_2.png) [@Khanh\_Nguyen](https://discuss.aerospike.com/u/Khanh_Nguyen)\
**Post date:** [September 9, 2022, 1:13am UTC](https://discuss.aerospike.com/t/storage-engine-config-cannot-be-changed-kubernetes/9726/1 "2022-09-09T01:13:11Z")

</div>

Hello, I am super new to aerospike. We have it running on EKS and I am tasked with updating **filesize**. My CR consists on this block.

```
namespaces:
  - name: test
    memory-size: 7000000000
    replication-factor: 2
    nsup-period: 60
    storage-engine:
      type: device
      files:
        - /opt/aerospike/data/event_collection.dat
      filesize: 10000000000
      data-in-memory: true

```

When I change filesize to anything besides what it currently is (like down to 9000000000 or up 11000000000), I get this error why doing kubectl apply

“Resource: “[asdb.aerospike.com/v1beta1](http://asdb.aerospike.com/v1beta1), Resource=aerospikeclusters”, GroupVersionKind: “[asdb.aerospike.com/v1beta1](http://asdb.aerospike.com/v1beta1), Kind=AerospikeCluster” Name: “aerocluster”, Namespace: “aerospike” for: “aerospike-cluster4.yaml”: admission webhook “[vaerospikecluster.kb.io](http://vaerospikecluster.kb.io)” denied the request: storage-engine config cannot be changed.”

Do you know what I am doing wrong?

---

<div class="post-metadata">

**Author:** ![Khanh\_Nguyen](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/khanh_nguyen/32/1940_2.png) [@Khanh\_Nguyen](https://discuss.aerospike.com/u/Khanh_Nguyen)\
**Post date:** [September 12, 2022, 3:43pm UTC](https://discuss.aerospike.com/t/storage-engine-config-cannot-be-changed-kubernetes/9726/2 "2022-09-12T15:43:01Z")

</div>

We were able to resolve by implementing rackconfig: [Scaling Namespace Storage | Aerospike Documentation](https://docs.aerospike.com/cloud/kubernetes/operator/Scaling-namespace-storage)

The trick is to add a racks.aerospikeConfig.namespaces block as their own config. The default namespaces block must be left alone and unchanged. My mistake by changing the original spec.aerospikeConfig.namespaces block instead of creating an entirely new entry inside rackconfig.racks.aerospikeConfig.namespaces.

After kubectl apply, the data will begin to migrate to the new volumes and logs can be viewed in aerospike operator logs and also by ssh into individual containers and looking at the .dat directory/file.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [December 5, 2022, 3:43pm UTC](https://discuss.aerospike.com/t/storage-engine-config-cannot-be-changed-kubernetes/9726/3 "2022-12-05T15:43:37Z")

</div>

This topic was automatically closed 84 days after the last reply. New replies are no longer allowed.