Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove cluster setup #6081

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/website/blog/2022-06-14-binding-external-service.md
Expand Up @@ -85,7 +85,7 @@ stringData:
To be able to *mount* the values of this secret from any namespace, you can use the *Service Binding Operator* (SBO for short), so each developer can define a ServiceBinding resource
between the service and its application, and get the values of the secret (and other values) mounted into its application's Pod.

You can find information about the Service Binding Operator [here](/docs/overview/cluster-setup/kubernetes).
You can find information about the Service Binding Operator [here](/docs/command-reference/add-binding#installing-the-service-binding-operator).

A ServiceBinding defines a binding between an *Application* and a *Service*. The credentials injected into the application
can be defined in different ways:
Expand Down
7 changes: 6 additions & 1 deletion docs/website/docs/command-reference/add-binding.md
Expand Up @@ -21,10 +21,15 @@ To know about the Operators supported by the Service Binding Operator, read its
## Running the Command

### Pre-requisites
* A cluster with the Service Binding Operator installed (see installation instructions for [Kubernetes](../overview/cluster-setup/kubernetes.md#installing-the-service-binding-operator) and [OpenShift](../overview/cluster-setup/openshift.md#installing-the-service-binding-operator) cluster)
* A cluster with the Service Binding Operator installed
* Operator-backed services or resources you want to bind your application to
* Optional, a directory containing a Devfile; if you don't have one, see [odo init](init.md) on obtaining a devfile.

#### Installing the Service Binding Operator
Service Binding Operator is required to bind an application with microservices.

Visit the [official documentation](https://redhat-developer.github.io/service-binding-operator/userguide/getting-started/installing-service-binding.html#installing-the-service-binding-operator-from-the-openshift-container-platform-web-ui) of Service Binding Operator to see how you can install it on your OpenShift cluster.

### Interactive Mode
In the interactive mode, you will be guided to choose:
* the namespace containing the service instance you want to bind to,
Expand Down
4 changes: 0 additions & 4 deletions docs/website/docs/overview/cluster-setup/_category_.json

This file was deleted.

45 changes: 0 additions & 45 deletions docs/website/docs/overview/cluster-setup/kubernetes.md

This file was deleted.

19 changes: 0 additions & 19 deletions docs/website/docs/overview/cluster-setup/openshift.md

This file was deleted.

1 change: 0 additions & 1 deletion docs/website/docs/user-guides/quickstart.md
Expand Up @@ -18,7 +18,6 @@ A full list of example applications can be viewed with the `odo registry` comman
## Prerequisites

* Have the odo binary [installed](../overview/installation.md).
* A [Kubernetes](../overview/cluster-setup/kubernetes) or [OpenShift cluster](../overview/cluster-setup/openshift)

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
Expand Down