Create a staging OCP4 cluster in AWS for CI. This will also have the benefit of helping to scope the production deployment
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: centos-ci-infra, high-gain, high-trouble, mini-initiative
Metadata Update from @arrfab: - Issue assigned to mobrien
Metadata Update from @zlopez: - Issue priority set to: High Priority (was: Waiting on Assignee)
Openshift aws cluster is up, idp is configured to authenticate from aco/fas but not group mappings. Efs storage is created and storage solutions being investigated
Metadata Update from @mobrien: - Issue priority set to: Waiting on Assignee (was: High Priority)
Metadata Update from @arrfab: - Issue assigned to arrfab (was: mobrien)
Due to some constraints, we decided to redeploy a different STG cluster, and status update is that we now have https://console-openshift-console.apps.ocp.cloud.stg.ci.centos.org/dashboards deployed.
We'll be working on :
Cluster had to be redeployed with some VPC/network tuned settings but all working again. Working now :
Last step before we'll deploy the production cluster is just to test to migrate one jenkins from old to new and see how it goes (we'll not do that for tenants but can give them pointers)
@zlopez and @phsmoura will have a look but whole cluster is now deployed/ready in .stg. and also our jenkins deployment templates rolled-out and tested
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.