acm-upgrade-scheduler PoC #4417
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maorfr
force-pushed
the
acm-upgrade-scheduler
branch
from
0c6538f
to
e4acad1
Compare
maorfr
force-pushed
the
acm-upgrade-scheduler
branch
from
e4acad1
to
7117a8f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
part of https://issues.redhat.com/browse/APPSRE-10308
this is an attempt to run a flavor of AUS side-by-side with an ACM instance.
this integration is meant to be run in a context of a VERY small app-interface: https://gitlab.cee.redhat.com/service/acm-aus-poc
this PoC relies on annotations on ManagedCluster CRs. how did these annotations get there? https://gitlab.cee.redhat.com/service/app-interface/-/blob/f934a2cf6d41c8ce31e7d7cb0ab91900881ba033/resources/services/advanced-cluster-management/managed-cluster.yaml.j2#L8