fix: moving monitor configs to named clusters #5174
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
|
@theflockers: No jobs can be run with The following commands are available to trigger optional jobs: 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-sigs/prow repository. |
|
/approve |
|
/ok-to-test |
|
/approve |
|
@hugares could you take a look in this PR? I am not sure if the way done here it would load the resources as expected, so loading the configs from the "staging" directories for different clusters. |
|
/retest |
Signed-off-by: Leandro Mendes <lmendes@redhat.com>
theflockers
force-pushed
the
moving-configmap
branch
from
4211e77 to
724b181
Compare
|
New changes are detected. LGTM label has been removed. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: seanconroy2021, theflockers 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 |
|
/ok-to-test |
|
/test all |
|
@theflockers: No jobs can be run with The following commands are available to trigger optional jobs: 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-sigs/prow repository. |
No description provided.