NO-ISSUE: automate OCP-46422 and adding in-cluster Cincinnati#1354
NO-ISSUE: automate OCP-46422 and adding in-cluster Cincinnati#1354JianLi-RH wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: JianLi-RH The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
469fa60 to
3963e80
Compare
0cad08f to
04fba21
Compare
|
Test passed on my local machine: Cluster-bot log: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/release-openshift-origin-installer-launch-aws-modern/2037388148400459776 |
04fba21 to
5fc7d7e
Compare
With below new methods, we can create upstream cincinnati independently. CreateGraphTemplate() will help create a upstream graph template. RunUpdateService() will add upstream graph to a test pod. CreateService() will create a service. CreateNetworkPolicy() will create a network policy. CleanupService() will delete a service. DeleteDeployment() will delete a deployment. PatchUpstream() will patch upstream and channel. DeleteNetworkPolicy() will delete a network policy. Typically we follow below steps to create cincinnati: 1. CreateGraphTemplate - Create a graph text 2. RunUpdateService - Create a pod by deployment which host above graph 3. CreateService - Create graph url by creating UpdateService 4. CreateNetworkPolicy - Create a network policy which help us publish the graph url 5. PatchUpstream - Pathch above graph url and channel to cluster
5fc7d7e to
8d7f449
Compare
|
/cc @hongkailiu @jiajliu |
|
@JianLi-RH: This pull request explicitly references no jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@JianLi-RH: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
As we discussed in https://redhat-internal.slack.com/archives/CJ1J9C3V4/p1773852594419879?thread_ts=1773825774.280769&cid=CJ1J9C3V4
we can generate Cincinnati json and inject it to a test pod, then we use the pod's service URI for upstream.
This PR implements some common methods and finished test case: https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-46422