Crossplane creates multiple AWS EBS volumes while reconciling

[sharigitpersonal]

What happened?

Created an EBS volume using crossplane and aws provider 'registry.upbound.io/crossplane/provider-aws:v0.23.0' . The volume was created with the exact configurations that I passed.

I tried to delete the volume manually to check the reconciliation feature of crossplane. But it started creating many volumes. It created almost 2k volumes and flooded the system.

I would like to understand how the reconciliation must be approached in data storage resources. Is there any changes that we need to do in the resource yaml to avoid such flooding of resource creations.

How can we reproduce it?

What environment did it happen in?

Crossplane version: crossplane/crossplane:v1.6.2 Ran in Kops Kubernetes 1.16

cat /etc/os-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal

uname -a Linux ip-10-0-90-170 5.13.0-1014-aws crossplane/crossplane#15~20.04.1-Ubuntu SMP Thu Feb 10 17:55:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

This is the Yaml that I used to create the volume in AWS.

apiVersion: ec2.aws.crossplane.io/v1alpha1
kind: Volume
metadata:
  name: crossplane
spec:
  forProvider:
    region: us-east-1
    availabilityZone: us-east-1a
    encrypted: true
    kmsKeyId:  <samplekey>
    volumeType: gp3
    size: 1
    tagSpecifications:
      - tags:
          - key: name
            value: test
        resourceType: volume
  providerConfigRef:
    name: default 
![volumeflood](https://user-images.githubusercontent.com/42409961/158129913-4687a4c3-9f2f-45fd-b728-d0480a8df199.JPG)

[haarchri]

@sharigitpersonal can we have this topic in crossplane/provider-aws ? btw never see something like this in our environment but i can check

[haarchri]

@jbw976 can you move this bug to provider-aws ?

[ra0e]

What is the actual status on this @haarchri ?

[github-actions[bot]]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.