-
Notifications
You must be signed in to change notification settings - Fork 36
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
Externalize ansible variables #163
Externalize ansible variables #163
Conversation
@electrocucaracha: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
1 similar comment
/retest |
/retest |
Signed-off-by: Victor Morales <v.morales@samsung.com>
Signed-off-by: Victor Morales <v.morales@samsung.com>
Signed-off-by: Victor Morales <v.morales@samsung.com>
Signed-off-by: Victor Morales <v.morales@samsung.com>
9a5db27
to
4bf1d89
Compare
Signed-off-by: Victor Morales <v.morales@samsung.com>
Signed-off-by: Victor Morales <v.morales@samsung.com>
4bf1d89
to
946d1eb
Compare
The failure is in the last e2e test, the SMF scaling:
This is a flake, it's not related to the PR. The issue is that a new package revision is getting created by some controller, and this e2e test doesn't expect that. It's some timing issue with a controller, I saw a similar thing once in my testing too. It can be fixed with a more robust implementation of the e2e test that takes into account that another actor could be changing the package. I will raise an issue to work on that. /retest |
Different flake :( SMF never fully deployed for some reason. /retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: electrocucaracha, johnbelamaric The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This change refactors some Ansible Roles to expose some variables and allow users to adjust them to their needs. It fixes some linting issues, removes some leftovers, and breaks down some playbooks to make them easier to understand. It also adds the documentation for the
kpt
role.Which issue(s) this PR fixes:
NA
Special notes for your reviewer:
Does this PR introduce a user-facing change?: