This is a followup to https://pagure.io/fedora-infrastructure/issue/7825.
We have had good progress on the coreos-cincinnati side, and we think most of the business logic has been sorted out at this point. The staging cluster served us well so far, and now we'd like to deploy on the production cluster too, and start pointing clients at it.
The openshift-apps/coreos-cincinnati.yml should be already ready for being dual-hosted on stg & prod.
openshift-apps/coreos-cincinnati.yml
This is a live ticket to track all tasks (feel free to add any missing ones). Still pending: - [x] sign-off from app-owners - [x] sign-off from infra team - [x] update hosts in playbook - [x] update proxy setup (after end-of-freeze)
hosts
/cc @dustymabe
Infra team approves this
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: OpenShift
Can we get some updates on this?
@lucab you should be able to self serve yourself on this now. Let's us know if you need anything else.
Thanks. No explicit blockers, except I don't have time to focus on this right now. I'll update this ticket once I have some progress.
The project is deployed, all OpenShift objects are properly in place.
However the service doesn't work, I believe there is some HTTPS reverse proxy in front of it which needs at least the following adjustments: * TLS certs valid for the domains at https://os.fedoraproject.org/console/project/coreos-cincinnati/browse/services/coreos-cincinnati?tab=details. * Mappings for all the routes above.
As a quick standalone test to check whether the service is operational, just run the following (with .stg removed): curl -H 'Accept: application/json' 'https://updates.coreos.stg.fedoraproject.org/v1/graph?basearch=x86_64&stream=testing&rollout_wariness=0'
.stg
curl -H 'Accept: application/json' 'https://updates.coreos.stg.fedoraproject.org/v1/graph?basearch=x86_64&stream=testing&rollout_wariness=0'
Yeah, there's a few conditionals in the proxy setup that are staging only. ;(
Can we wait and do this after beta is out the door? Or would you like me to prep a freeze break request with the needed changes?
@kevin no hurry, we can continue after the freeze (and, thanks!). Let's just keep the top ticket updated with ongoing status.
ok, freeze is over and I pushed proxy changes.
Can you test and confirm all is now working?
If not, re-open and we can debug, but I think it's all set.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Ack, everything confirmed working.
@kevin once again, thanks for your work!
Login to comment on this ticket.