Now that we have the automatic and the SSM resolvers for AMIs I think we can deprecate the static one.

Describe the solution you'd like
It would be neat to see the start time of plugins when looking at sonobuoy status. For example, when E2E are running, they may take a while, but when did they start?

$ sonobuoy status                                                                                                            
PLUGIN		STATUS		COUNT
e2e		running		1
systemd_logs	comple

PR o'clock

Description

1. Add ingress rule to workers and cluster security groups to allow Fargate pods to communicate with EC2 nodes
2. Allow EKS Fargate profiles to be created via input eks_fargate_profiles = [...]. This also creates an IAM role for pod execution and extends the aws-auth ConfigMap.

Checklist

• CI tests are passing
• README.md has been updated aft

OS running on Ansible host:

NA

Ansible Version (ansible --version):

NA

Uploaded logs showing errors(`rak8s/.log/ansi

Works in Safari, Chrome for Mac, Chrome for PC, Edge, but not IE version 11.192.16299.0 on Windows 10

The command line should be able to display the pupernetes version.

There's a ssh_config fixture to simplify things a bit:

def given_check_pod_status(ssh_config, host, k8s_client, label, expected_status):

Originally posted by @gdemonet in scality/metalk8s#2369