Skip to content

Commit

Permalink
Remove the run-console-local Makefile target
Browse files Browse the repository at this point in the history
Signed-off-by: timflannagan <timflannagan@gmail.com>
  • Loading branch information
timflannagan committed Apr 18, 2022
1 parent c36183e commit e931a5e
Show file tree
Hide file tree
Showing 3 changed files with 1 addition and 85 deletions.
5 changes: 0 additions & 5 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -254,11 +254,6 @@ endif
# OLM - Install/Uninstall/Run #
################################

.PHONY: run-console-local
run-console-local:
@echo Running script to run the OLM console locally:
. ./scripts/run_console_local.sh

.PHONY: uninstall
uninstall:
@echo Uninstalling OLM:
Expand Down
14 changes: 1 addition & 13 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,18 +56,6 @@ Install OLM on a Kubernetes cluster by following the [installation guide][instal

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).

## User Interface (Running the console Locally)

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.

Ensure `kubectl` is pointing at a cluster and run:

```shell
make run-console-local
```

Then visit `http://localhost:9000` to view the console.

## Contributing your Operator

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/).
Expand Down Expand Up @@ -97,7 +85,7 @@ Learn more about the components used by OLM by reading about the [architecture]

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.

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),
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),
[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)

## Descriptors
Expand Down
67 changes: 0 additions & 67 deletions scripts/run_console_local.sh

This file was deleted.

0 comments on commit e931a5e

Please sign in to comment.