1.29/beta - AWS cloud integration fails to start the cloud-provider deployments

[Adam Dyess]

The reactive versions of these charms requested a set of permissions over the `aws` integration relation to provide the instances with permissions within aws to run the cloud-provider.

Here's a snipped of the error from the AWS cloud-provider running on an upgraded cloud:

F0108 21:57:30.416427 1 main.go:106] Cloud provider could not be initialized: could not init cloud provider "aws": error finding instance i-0bc0d56ec6607c7b1: "error listing AWS instances: \"AuthFailure: AWS was not able to validate the provided access credentials\\n\\tstatus code: 401, request id: 94e80e43-5f7d-4aef-971d-36d59ca62332\""

I believe the missing gaps are within the aws-integration integration -- neither the control-plane charm [0] nor the worker charm [1] sets tags on the ec2 instances to help the cloud-provider with info necessary to operate. There also seems to be some other integrations which may be missing for other clouds such as azure and gcp.

We should consider adding these back into the reconciliation loop to re-enable cloud features

[0](https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/blob/reactive-archive/reactive/kubernetes_control_plane.py#L2959-L3015)
[1](https://github.com/charmed-kubernetes/charm-kubernetes-worker/blob/reactive-archive/reactive/kubernetes_worker.py#L1169-L1213)

[Kevin W Monroe (kwmonroe)]

This is scheduled for the 1.29+ck1 release.

[Adam Dyess (addyess)]

Neither of these were backported to the 1.29 branch.

kubernetes-worker
  https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/165/
kubernetes-control-plane
  https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/pull/337

[Adam Dyess (addyess)]

https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/pull/355

[Adam Dyess (addyess)]

Backport to 1.30

https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/commit/df358857df566d0410f9118b6c11070417b738ac