aerospike-kubernetes-operator icon indicating copy to clipboard operation
aerospike-kubernetes-operator copied to clipboard

.podSpec.multiPodPerHost missing from result AerospikeCluster

Open noam-ma-ma opened this issue 5 months ago • 3 comments

Issue Details

When the AerospikeCluster CRD is applied with the ".podSpec.multiPodPerHost" field, the resulting target AerospikeCluster CRD does not contain this field, despite it being clearly mentioned in the kubectl.kubernetes.io/last-applied-configuration metadata.annotation. I'm using aerospike-operator v3.2.0.

Steps to Reproduce:

To reproduce this issue, follow these steps:

  1. Apply an AerospikeCluster CRD with ".podSpec.multiPodPerHost"
  2. Check the resulting target CRD and observe that the field is missing.

Expected Behavior:

After applying the CRD, the target CRD should reflect the same configuration as the kubectl.kubernetes.io/last-applied-configuration metadata.annotation and contain the ".podSpec.multiPodPerHost" field.

Impact

When using AerospikeCluster with ArgoCD, the object is always "out of sync" (left is the cluster object, right is the git manifest) Screenshot 2024-02-01 at 14 46 56

noam-ma-ma avatar Feb 01 '24 12:02 noam-ma-ma