Application Life Cycle Examples | Developer Guide

Overview
Developing on OKD
Developing Then Deploying on OKD

Overview

As a PaaS, OKD is designed for building and deploying applications. Depending on how much you want to involve OKD in the development process, you can choose to develop on OKD and use it to continuously develop an application, or you can deploy a fully developed application onto an OKD instance.

Developing on OKD

You can develop your application on OKD directly. Use the following process if you plan to use OKD as a method to build and deploy your application:

Initial Planning

What does your application do?
What programming language will it be developed in?

Access to OKD

OKD should be installed by this point, either by yourself or an administrator within your organization.

Develop

Using your editor/IDE of choice, create a basic skeleton of an application. It should be developed enough to tell OKD what kind of application it is.
Push the code to your Git repository.

Generate

Create a basic application using the new-app command. OKD generates build and deployment configurations.

Manage

Start developing your application code.
Ensure your application builds successfully.
Continue to locally develop and polish your code.
Push your code to a Git repository.
Is any extra configuration needed? Explore the Developer Guide for more options.

Verify

You can verify your application in a number of ways. You can push your changes to your application’s Git repository, and use OKD to rebuild and redeploy your application. Alternatively, you can hot deploy using rsync to synchronize your code changes into a running pod.

Developing Then Deploying on OKD

Another possible application life cycle is to develop locally, then use OKD to deploy your fully developed application. Use the following process if you plan to have application code already, then want to build and deploy onto an OKD installation when completed: