Skip to content

Move logos into their own directory #2746

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

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
<img src="/logo.svg#gh-light-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
<img src="/logo-dark-mode.svg#gh-dark-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
<img src="logo/logo.svg#gh-light-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>
<img src="logo/logo-dark-mode.svg#gh-dark-mode-only" height="125px" alt="Operator Lifecycle Manager"></img>

[![Container Repository on Quay.io](https://quay.io/repository/operator-framework/olm/status "Container Repository on Quay.io")](https://quay.io/repository/operator-framework/olm)
[![License](http://img.shields.io/:license-apache-blue.svg)](http://www.apache.org/licenses/LICENSE-2.0.html)
Expand All @@ -10,7 +10,6 @@

User documentation can be found on the [OLM website][olm-docs].


## Overview

This project is a component of the [Operator Framework](https://github.com/operator-framework), an open source toolkit to manage Kubernetes native applications, called Operators, in an effective, automated, and scalable way. Read more in the [introduction blog post](https://operatorhub.io/what-is-an-operator) and learn about practical use cases at the [OLM website][olm-docs].
Expand Down Expand Up @@ -100,10 +99,10 @@ To minimize the effort required to run an application on kubernetes, OLM handles

This is achieved through additional metadata on the application definition. Each operator must define:

- The CRDs that it is responsible for managing.
- e.g., the etcd operator manages `EtcdCluster`.
- The CRDs that it depends on.
- e.g., the vault operator depends on `EtcdCluster`, because Vault is backed by etcd.
- The CRDs that it is responsible for managing.
- e.g., the etcd operator manages `EtcdCluster`.
- The CRDs that it depends on.
- e.g., the vault operator depends on `EtcdCluster`, because Vault is backed by etcd.

Basic dependency resolution is then possible by finding, for each “required” CRD, the corresponding operator that manages it and installing it as well. Dependency resolution can be further constrained by the way a user interacts with catalogs.

Expand Down
3 changes: 3 additions & 0 deletions logo/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# Logo

Home for the OLM related logos.
File renamed without changes
File renamed without changes
File renamed without changes