Skip to content

Commit 1f00178

Browse files
authored
Remove the run-console-local Makefile target (#2744)
Signed-off-by: timflannagan <[email protected]>
1 parent c36183e commit 1f00178

File tree

3 files changed

+1
-85
lines changed

3 files changed

+1
-85
lines changed

Makefile

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -254,11 +254,6 @@ endif
254254
# OLM - Install/Uninstall/Run #
255255
################################
256256

257-
.PHONY: run-console-local
258-
run-console-local:
259-
@echo Running script to run the OLM console locally:
260-
. ./scripts/run_console_local.sh
261-
262257
.PHONY: uninstall
263258
uninstall:
264259
@echo Uninstalling OLM:

README.md

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -56,18 +56,6 @@ Install OLM on a Kubernetes cluster by following the [installation guide][instal
5656

5757
For a complete end-to-end example of how OLM fits into the Operator Framework, see the [Operator Framework website](https://operatorframework.io/about/) and the [Getting Started guide on OperatorHub.io](https://operatorhub.io/getting-started).
5858

59-
## User Interface (Running the console Locally)
60-
61-
Use the admin console to interact with and visualize the resources managed by OLM. Create subscriptions, approve install plans, identify Operator-managed resources, and more.
62-
63-
Ensure `kubectl` is pointing at a cluster and run:
64-
65-
```shell
66-
make run-console-local
67-
```
68-
69-
Then visit `http://localhost:9000` to view the console.
70-
7159
## Contributing your Operator
7260

7361
Have an awesome Operator you want to share? Checkout the [publishing docs](https://operatorhub.io/contribute) to learn about contributing to [OperatorHub.io](https://operatorhub.io/).
@@ -97,7 +85,7 @@ Learn more about the components used by OLM by reading about the [architecture]
9785

9886
OLM standardizes interactions with operators by requiring that the interface to an operator be via the Kubernetes API. Because we expect users to define the interfaces to their applications, OLM currently uses CRDs to define the Kubernetes API interactions.
9987

100-
Examples: [EtcdCluster CRD](https://github.com/redhat-openshift-ecosystem/community-operators-prod/blob/main/operators/etcd/0.9.4/etcdclusters.etcd.database.coreos.com.crd.yaml),
88+
Examples: [EtcdCluster CRD](https://github.com/redhat-openshift-ecosystem/community-operators-prod/blob/main/operators/etcd/0.9.4/etcdclusters.etcd.database.coreos.com.crd.yaml),
10189
[EtcdBackup CRD](https://github.com/redhat-openshift-ecosystem/community-operators-prod/blob/main/operators/etcd/0.9.4/etcdbackups.etcd.database.coreos.com.crd.yaml)
10290

10391
## Descriptors

scripts/run_console_local.sh

Lines changed: 0 additions & 67 deletions
This file was deleted.

0 commit comments

Comments
 (0)