If you are a system administrator or otherwise have sufficient permissions, change to the openshift project. Using the openshift project allows you to globally update the image stream definitions.

$ oc project openshift

If you do not have permissions to use the openshift project, you can still update your project definitions starting with Step 2.

Run the following command to list all available .NET Core image versions.

$ oc describe is dotnet

The output shows installed images or the message Error from server (NotFound) if no images are installed.

To pull the images, OpenShift needs credentials for authenticating with the registry.redhat.io server. These credentials are stored in a secret.

Enter the following command to list secrets. The first column shows the secret name.

$ oc get secret | grep kubernetes.io/dockercfg

To check the contents of a secret, you can decode the .dockercfg or .dockercfgjson data from Base64 format. This allows you to see if you already have credentials for the registry.redhat.io server. Enter the following command to show the .dockercfg section in a secret.

$ oc get secret <secret-name> -o yaml | grep .dockercfg
  .dockercfg: eyJyZWdpc3RyeS5yZWRoYXQuaW8iOnsidXNlcm5hbWUiOiIqKioqKioqKiIsInBhc3N3b3JkIjoiKioqKioqKioiLCJlbWFpbCI6InVudXNlZCIsImF1dGgiOiJLaW9xS2lvcUtpbzZLaW9xS2lvcUtpbz0ifX0=

Copy and paste the output in the following command to convert it from Base64 format. The example below shows the credentials for the registry.redhat.io server.

$ echo eyJyZWdpc3RyeS5yZWRoYXQuaW8iOnsidXNlcm5hbWUiOiIqKioqKioqKiIsInBhc3N3b3JkIjoiKioqKioqKioiLCJlbWFpbCI6InVudXNlZCIsImF1dGgiOiJLaW9xS2lvcUtpbzZLaW9xS2lvcUtpbz0ifX0= | base64 -d
{"registry.redhat.io":{"username":"********","password":"********","email":"unused","auth":"KioqKioqKio6KioqKioqKio="}}

You need to add a secret if there is no secret listed with credentials for the registry.redhat.io server.

Red Hat account credentials are used for registry.redhat.io access. If you are a customer with entitlements to Red Hat products, you already have account credentials to use. These are typically the same credentials used to log in to the Red Hat Customer Portal. To verify your Red Hat credentials, enter the following command and attempt to log in.

$ docker login registry.redhat.io

If you cannot log in, you first need to get an account with Red Hat. See Red Hat Container Registry Authentication for additional information. If you can log in, enter the following commands to create the secret.

$ oc create secret docker-registry redhat-registry \
    --docker-server=registry.redhat.io \
    --docker-username=<user-name> \
    --docker-password=<password> \
    --docker-email=unused
$ oc secrets link default redhat-registry --for=pull
$ oc secrets link builder redhat-registry

After creating the secret, enter the following command to import new image streams.

$ oc create -f https://raw.githubusercontent.com/redhat-developer/s2i-dotnetcore/master/dotnet_imagestreams.json

If image streams were already installed, use the replace command to update the image stream definitions.

$ oc replace -f https://raw.githubusercontent.com/redhat-developer/s2i-dotnetcore/master/dotnet_imagestreams.json

Run the following commands to deploy the ASP.NET Core application, which is in the app folder on the dotnetcore-2.0 branch of the redhat-developer/s2i-dotnetcore-ex GitHub repository.

$ oc new-app --name=exampleapp 'dotnet:2.0~https://github.com/redhat-developer/s2i-dotnetcore-ex#dotnetcore-2.0' --build-env DOTNET_STARTUP_PROJECT=app

As suggested by the output of the new-app command, you can track progress of the build using the oc logs command.

$ oc logs -f bc/exampleapp

Once the build is finished, you can see the deployed application.

$ oc logs -f dc/exampleapp

At this point, the application is accessible within the project. To make it accessible externally, use the oc expose command. You can then use oc get routes to find the URL.

$ oc expose svc/exampleapp
$ oc get routes