[aws-eks] Support object pruning

[iliapolo]

Use Case

Currently, situations may arise that leave orphan resources. For example, consider the following manifest:

new eks.KubernetesManifest(this, 'Configs', {
  cluster,
  manifest: [
    {
      kind: 'ConfigMap',
      apiVersion: 'v1',
      metadata: {
        name: 'config1'
      },
      data: {
        foo: 'bar'
      }
    }, 
    {
      kind: 'ConfigMap',
      apiVersion: 'v1',
      metadata: {
        name: 'config2'
      },
      data: {
        hello: 'world'
      }
    }, 
  ]
})

When it is first deployed, we issue a kubectl apply command that creates both config maps.

If we now remove one config map, i.e the manifest will look like so:

new eks.KubernetesManifest(this, 'Configs', {
  cluster,
  manifest: [
    {
      kind: 'ConfigMap',
      apiVersion: 'v1',
      metadata: {
        name: 'config1'
      },
      data: {
        foo: 'bar'
      }
    } 
  ]
})

Since the CFN resource is the same, just its properties changed, an UPDATE call be executed by CFN, which will simply translate into a kubectl apply on the new manifest, which will not delete the config map that was removed from the manifest.

Proposed Solution

• Automatically add pruning labels to all resources and use kubectl apply --prune (see pruning objects)

• Before running kubectl apply on update, run kubectl delete on the previous manifest (available as as CFN property at invocation time)

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.