3 years ago

Category: Business, Security, Infrastructure, Jenkins, Architecture

by The previous articles were introducing the foundations of a blueprint for cloud-native development, exploring a logical diagram, and diving into the first use cases with cloud-native development on local, remote containers, and a look at a deployment blueprint. This article completes the series with a look at the advanced cloud-native deployment blueprint.

At this point it has been tagged as appImage:dev and is pushed to the OpenShift cluster hosting the enterprise image registries managed with Quay.

All eventual dev tagged images, such as our appImage:dev container image is pushed out to the development infrastructure for further testing.