Skip to content
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.

A guide on how to bring a new infrastructure provider to OpenShift Container Platform

License

Notifications You must be signed in to change notification settings

elmiko/ocp-infrastructure-provider-onboarding-guide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OCP Infrastructure Provider Onboarding Guide

ATTENTION This repository has been archived in favor of the new canonical source, please address all future changes and issues to:

openshift/infrastructure-provider-onboarding-guide


A guide on how to bring a new infrastructure provider to OpenShift Container Platform.

The documentation in this repository is organized to use the Mkdocs site generation tool. In general the site can be viewed by running mkdocs serve from the root of the project repository and then visiting http://localhost:8000 with a web browser.

Contributing to this repository

All the documentation in this repository is in Markdown format, and is located in the docs directory. When adding new documents, remember to add an entry in mkdocs.yml file under the nav section if you will need a link in the navigation bar (see the MkDocs User Guide for more details).

When proposing changes, please open a pull request with your change from a feature branch on a fork of this repository.

About

A guide on how to bring a new infrastructure provider to OpenShift Container Platform

Resources

License

Stars

Watchers

Forks

Packages

No packages published