Migrate to OCP4

[bcgov]

Migrate to OCP4

[esune]

@WadeBarnes: as discussed, the tails server was setup and is ready to go in all environments. A new sync of the files stored by the old one will be required before we switch over, as well as coordination to ensure the DNS entries are updated correctly when the time comes.

[esune]

The only thing left to do is turning off the old tails servers - this coming friday. Maybe we should keep this open until we do that and then wrap up everything.

[esune]

@wadeking98 I have not yet thought through 100% what to do with the pipelines, but I think as a first step ensuring the components based on issuer-kit respect the same naming convention we put together for essential-services-delivery is a good step. That means the build configurations must be named and labelled the same way (so that they result in exactly the same output) and the deployment configurations must reference those image names.

Additionally, for the a2a profile please make sure that the appropriate value for PROJECT_NAMESPACE is set in settings.a2a.sh as the app will be deployed in a different OCP namespace than the other services.

[esune]

All services have been migrated successfully.

@wadeking98 is in the process of migrating the data for vc-authn and updating the apps that connect directly to it (e.g.: the visual verifiers) to use the new OCP4 urls.

Please note: since we have two instances of vc-authn (one supporting revocation and the other not supporting it) make sure the URL used to update the visual-verifier secret(s) is the appropriate one.

[wadeking98]

@esune are we free to close this now?

[esune]

Tails servers have been migrated, so this can be closed now.