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

[tenant-namespace-operator] Fixed Ansible issues with unsafe yaml #71

Merged
merged 1 commit into from
Nov 13, 2023

Conversation

plnordquist
Copy link

  • Loaded the CR data using k8s_info so it is loaded unsafe
  • Switched variable references to new CR var
  • Updated variable references for Ansible best practices (snake case)
  • Prepended underscore to variables to avoid clashes with operator snake case variables

Loaded the CR data using k8s_info so it is loaded unsafe
Switched variable references to new CR var
Updated variable references for Ansible best practices (snake case)
Prepended underscore to variables to avoid clashes with operator snake
case variables
Copy link

@kfox1111 kfox1111 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks very good. Thanks!

A couple small questions inline.

Copy link

@kfox1111 kfox1111 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks! :)

@plnordquist
Copy link
Author

Tested again the behavior of the when blocks and I didn't see any issues. When metallb is not deployed it does not fail the playbook because of the missing IP. Also, I tested the behavior of setting a specific loadBalancerIP and that still works the same way as before.

@plnordquist plnordquist merged commit c2ff188 into pnnl-miscscripts:master Nov 13, 2023
@plnordquist plnordquist deleted the tno-unsafe branch April 2, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants