[BUG] `filebeat` communication error for AKS

Describe the bug During installation filebeat get host as hostname, this name isn’t added into /etc/hosts so after installation filebeat cannot resolve it, so cannot communicate to AKS

How to reproduce Steps to reproduce the behavior:

1. execute epicli init ... (with params)
2. edit config file
3. execute epicli apply ...

Expected behavior filebeat communicate properly

Config files n/a

Environment

• Cloud provider: Azure
• OS: Ubuntu 18.04.5 LTS

epicli version: 0.10.0

Additional context n/a

---

DoD checklist

• Changelog updated (if affected version was released)
• COMPONENTS.md updated / doesn’t need to be updated
• Automated tests passed (QA pipelines)
  • apply
  • upgrade
• Case covered by automated test (if possible)
• Idempotency tested
• Documentation updated / doesn’t need to be updated
• All conversations in PR resolved
• Backport tasks created / doesn’t need to be backported

[wkalbar]

@mkyc little update (and possible solution): We’ve dig deeper into this, and problem isn’t on epiphany cluster side, but on AKS pods configuration. There are filebeat pods in namespace epi-logging , named filebeat-filebeat-[5 alphanumeric id here], for example filebeat-filebeat-mnl8p This pods during epicli apply get hostname of our logging vm, but this hostname is unresolvable for them. We can manually add it to /etc/hosts on this pod, but if this pod/node next creation this entry will be deleted.

Solution working for us now is to edit daemonsets object (kubectl -n epi-logging edit daemonset filebeat-filebeat) and add block:

      - hostnames:
        - prefix-clustername-logging-vm-0
        ip: ip.address.of.logging.vm

After this, every new pod created will have in his /etc/hosts entry like below:

# Entries added by HostAliases.
ip.address.of.logging.vm     prefix-clustername-logging-vm-0

Now for this issue it should be added during epicli apply in filebeat part, or loging vm ip address should be added instead of hostname.

[mkyc]

@atsikham please create backport tasks to 0.9.x and 1.0.x.