-
Notifications
You must be signed in to change notification settings - Fork 80
Open
Labels
enhancementNew feature or requestNew feature or request
Description
๐ Description
This is an epic issue to track the effort needed to upgrate to OpenShift 4.20. These are at least the things that I can think of:
- Full removal of DeploymentConfigs. Currently the following components are still deployed using DCs:
- pet-battle-api MongoDB (Both for normal deployment and Blue/Green).
- pet-battle frontend Helm Chart.
- Sonarqube postgreSQL.
- Keycloak upstream operator does not ship version v19 of the operator in OCP 4.20 so we have to migrate to RHBK 2.24.
- I already started the work creating a new chart that I think that would work.https://github.com/petbattle/pet-battle-infra/tree/main/rhbk
- The problem is that I expect to have to upgrade the Keycloak client in the NodeJS and Quarkus app to connect to it.
- All the Tekton tasks and Pipeline from the Chapter 3 are using the old
tekton.dev/v1beta1version of the API. This should be upgraded before bumping version. - HPA
autoscaling/v2beta2was removed in favor ofautoscaling/v2 - There are plenty of automations in the pipelines related to openshift cli image for 4.12. This is going to be an issue sooner or later. Specially because we rely of the token generation using the following configuration that I think that will dissapear:
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request