hugoprudente/ansible-role-envoyproxy

Ansible Role for Envoy Proxy

ansible-role-envoyproxy's Issues

Add extra distributions support

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Today we cover only 3 distributions on it's latest version.

• Debian 10 (buster)
• Centos 8
• Ubuntu 20.04 (focal)

This issue is to track the improvement and add other distros as:

• Amazon Linux 2
• SUSE/SLES 15
• Red Hat 8

And maybe other distros heavily used on servers too, open to suggestions.

HA Setup using pace_maker from ansible.community.

Describe the solution you'd like
Add the HA Setup for 2+ nodes using pace_maker for failover + extras

Describe alternatives you've considered
We can also add keepalived for an networking layer, but I think the application level is enough for how the Envoy Proxy works.

Fix issue with logrotate

Log rotate is failing the configuration due to the name of the configuration.

Add option for install a containerised envoyproxy in the bare host.

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Some companies are using containers to deploy all the applications and managing it with Ansible similar to what Kolla does for Openstack.

The idea is to use the official container provided by EnvoyProxy or use a regsitry entry and start the container using 2 alternatives:

• docker
• podman

Using docker-compose for both.

Improve molecule container prepare.yml to cover all distributions.

Is your feature request related to a problem? Please describe.
Yes, due to the simple prepare.yml used I have hardcoded the tests to debian10 (buster).

This causes the MOLECULE_DISTRO not to be used creating a 2 false tests regarding on the GitHubActions matrix.

Describe the solution you'd like
Use the community roles to install and manage docker/podman to improve the prepare.yml and expand and cover to all distributions.

Copy Templates Error

When running this using the playbook in the tests directory... I receive this error:

amazon-ebs: TASK [envoy : Copy templates to default directory] *****************************

amazon-ebs: An exception occurred during task execution. To see the full traceback, use -vvv. 
The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'backends'. 
'dict object' has no attribute 'backends'
    
amazon-ebs: failed: [127.0.0.1] (item={'src': 'envoy.yaml.j2', 'dest': '/etc/envoy/envoy.yaml'}) => {"ansible_loop_var": "item", "changed": false, "item": {"dest": "/etc/envoy/envoy.yaml", "src": "envoy.yaml.j2"}, 
"msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'backends'. 'dict object' has no attribute 'backends'"}

How should backends be defined? Can you include that in the tests/test.yml playbook?

Ubuntu 20.04 - Repository is not signed.

Ubuntu 20.04

TASK [hugoprudente.envoyproxy : (Debian/Ubuntu) Configure Envoy Proxy repository] ************************************************************************************************************************************************
failed: [kochan_vm_20] (item=deb [arch=amd64] https://dl.bintray.com/tetrate/getenvoy-deb focal stable) => {"ansible_loop_var": "item", "changed": false, "item": "deb [arch=amd64] https://dl.bintray.com/tetrate/getenvoy-deb focal stable", "msg": "Failed to update apt cache: E:Failed to fetch https://dl.bintray.com/tetrate/getenvoy-deb/dists/focal/InRelease  403  Forbidden [IP: 34.209.123.136 443], E:The repository 'https://dl.bintray.com/tetrate/getenvoy-deb focal InRelease' is not signed."}

EnvoyProxy with --concurrency or --cpuset-threads

Describe the bug
Create the envoyproxy.system.conf.j2 to be able to manipulate the fields

• --cpuset-threads
• --concurrency

Additional context
Today the envoy proxy is starting with only 1 worker and this can be improved.
Also needs to add this to the container test in molecule to ensure that the behaviour is 100% covered in the tests.