Add k8s_event module to collection

[geerlingguy]

SUMMARY

A k8s_event module would be nice to have in certain circumstances. If you want to be able to add events attached to certain resources, this module could help you do that.

See: https://github.com/operator-framework/operator-metering/blob/master/images/metering-ansible-operator/roles/meteringconfig/library/k8s_event.py

ISSUE TYPE

• Feature Idea

ADDITIONAL INFORMATION

Example task:

- name: Create Kubernetes Event
  k8s_event:
    state: present
    name: test-https-emily109
    namespace: default
    message: Event created
    reason: Created
    reportingComponent: Reporting components
    type: Normal
    source:
      component: Metering components
    involvedObject:
      apiVersion: v1
      kind: Service
      name: test-https-emily107
      namespace: default

Note: This was migrated from ansible-collections/community.kubernetes#8

[tima]

[This is a larger issue than just this one instance. I'm not even sure which project to file it since it would span the K8s community collection, this one and hopefully more to come.]

We need to be consistent and establish a case convention for ansible+k8s parameters since they use different schemes which is unfortunate and annoying. Take reportingComponent or involvedObject in the example above for instance. I'm not 100% sure what the right thing is here.

My initial reaction is top level keys follow the Ansible convention (snake case) and complex data structures (that are part of the K8s API and probably getting pipe through it) can use the camelCase convention. I'm open to suggestions though.

[fabianvf]

Closed with #22