toversus/aws-ssm-operator

A Kubernetes operator for AWS SSM Parameter Store

aws-ssm-operator's Issues

CRD deprication warning

hey i had tried with CRD stable verion "apiextensions.k8s.io/v1" but whle making parameterstore it says
"error: error validating "ps.yaml": error validating data: ValidationError(ParameterStore): unknown field "spec" in aws.ssm.v1alpha1.ParameterStore; if you choose to ignore these errors, turn validation off with --validate=false".

how to increase secret sync limit from 10

I have used path based ssm operator to sync secrets from parameter store, but here i am able to sync only 10 secrets, I have approx 30 secrets to sync, where i need to modify this hard limit? Please help me.

Existing secret not being updated

aws-ssm-operator/pkg/controller/parameterstore/parameterstore_controller.go

Line 121 in 031c22d

} else if err != nil {

I think the following code change should fix it:

        // Check if this Secret already exists
        current := &corev1.Secret{}
        err = r.client.Get(context.TODO(), types.NamespacedName{Name: desired.Name, Namespace: desired.Namespace}, current)
        if err != nil {
                if errors.IsNotFound(err) {
                        reqLogger.Info("Creating a new Secret", "desired.Namespace", desired.Namespace, "desired.Name", desired.Name)
                        err = r.client.Create(context.TODO(), desired)
                }
        } else {
                reqLogger.Info("Updating an existing Secret", "desired.Namespace", desired.Namespace, "desired.Name", desired.Name)
                err = r.client.Update(context.TODO(), desired)
        }


        return reconcile.Result{}, err

Data is not populated with given path based example .

Hey , i was trying path based secret creation,

I created ssm paramstore secrets , as stated by your example. /stg/foo-app/dbuser and /stg/foo-app/dbpassword ,

aws-ssm-operator app deployed successfully , Provided SSM read access to EKS node role.

when after creatiing , kubectl create -f example/path/database.yaml

there is no Data in secret created.

Better solution (external-secrets.io)

At the moment of writing this issue this repo hasn't been updated for almost 2 years (1y and 8m). So I assuming it's not maintain anymore. Moreover there is much better (flexible) and well maintain project called external-secrets.io. It supports not only AWS Parameter Store but also AWS Secrets Manager, HashiCorp Vault, Google Secrets Manager, Azure Key Vault and many more.

Because of that I suggest to add this information to readme file with suggestion to use this project instead of this one and archive this repository.