You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inorder to keep costs in check, we have a kyverno policy deployed in our kubernetes clusters which requires that each PVC which is created have a certain annotation. The result of the annotation is that it applies tags on EBS volumes in AWS.
There is no option (Atleast in docs and CRDs) in the aerospike cluster CRD using which we can either add annotation in volumeClaimTemplate section of statefulsets created by the operator or directly on PVCs.
The annotation described above is a must have for us. We already did some workarounds in other applications (non aerospike), where we disable kyverno policy for that application specifically and add a cronjob which annotate the PVCs but its not a very clean solution and have to be maintained independently.
The text was updated successfully, but these errors were encountered:
Hi @sud82 , We are from Unity Technologies / Ironsource.
The above feature is required for mounting workdir on a persistentVolume and is basically a blocker for us migrating our aerospike clusters from EC2 to kubernetes
Inorder to keep costs in check, we have a kyverno policy deployed in our kubernetes clusters which requires that each PVC which is created have a certain annotation. The result of the annotation is that it applies tags on EBS volumes in AWS.
There is no option (Atleast in docs and CRDs) in the aerospike cluster CRD using which we can either add annotation in volumeClaimTemplate section of statefulsets created by the operator or directly on PVCs.
The annotation described above is a must have for us. We already did some workarounds in other applications (non aerospike), where we disable kyverno policy for that application specifically and add a cronjob which annotate the PVCs but its not a very clean solution and have to be maintained independently.
The text was updated successfully, but these errors were encountered: