Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: When Cilium config is changed, it is not properly applied #2

Closed
lukapetrovic-git opened this issue Dec 19, 2023 · 0 comments · Fixed by #3
Closed

[BUG]: When Cilium config is changed, it is not properly applied #2

lukapetrovic-git opened this issue Dec 19, 2023 · 0 comments · Fixed by #3
Labels
bug Something isn't working

Comments

@lukapetrovic-git
Copy link
Owner

Summary

Changing Cilium config does not apply the changes!

Ansible Version

ansible [core 2.15.8]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/luka/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  ansible collection location = /home/luka/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3)
  jinja version = 3.0.3
  libyaml = True

Repro Steps

  1. Run the role with 1 config.
  2. Run the role again with changed config.
  3. The config yaml changes, Cilium pods are restarted, but the config is not applied.

Expected Results

Expected the config changes to be applied when config changed.

Actual Results

Config changes were not applied when config changed.
@lukapetrovic-git lukapetrovic-git added the bug Something isn't working label Dec 19, 2023
lukapetrovic-git added a commit that referenced this issue Dec 19, 2023
Fixes #2 

Added running cilium upgrade on config changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant