Skip to content

Commit

Permalink
update: keda info
Browse files Browse the repository at this point in the history
  • Loading branch information
codekow committed Nov 3, 2023
1 parent 05ae244 commit 47da0c9
Showing 1 changed file with 6 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,14 @@
## About the managed application
Custom Metrics Autoscaler for OpenShift is an event driven autoscaler based upon KEDA. Custom Metrics Autoscaler can monitor event sources like Kafka, RabbitMQ, or cloud event sources and feed the metrics from those sources into the Kubernetes horizontal pod autoscaler. With Custom Metrics Autoscaler, you can have event driven and serverless scale of deployments within any Kubernetes cluster.
## About this Operator
The Custom Metrics Autoscaler Operator deploys and manages installation of KEDA Controller in the cluster. Install this operator and follow installation instructions on how to install Custom Metrics Autoscaler in you cluster.
The Custom Metrics Autoscaler Operator deploys and manages installation of KEDA Controller in the cluster. Install this operator and follow installation instructions on how to install Custom Metrics Autoscaler in your cluster.

## Prerequisites for enabling this Operator
## How to install Custom Metrics Autoscaler in the cluster
The installation of Custom Metrics Autoscaler is triggered by the creation of `KedaController` resource. Please refer to the [KedaController Spec](https://github.com/openshift/custom-metrics-autoscaler-operator/blob/main/README.md#the-kedacontroller-custom-resource) for more deatils on available options.
The installation of Custom Metrics Autoscaler is triggered by the creation of `KedaController` resource. Please refer to the [KedaController Spec](https://github.com/openshift/custom-metrics-autoscaler-operator/blob/main/README.md#the-kedacontroller-custom-resource) for more details on available options.

Only resource named `keda` in namespace `openshift-keda` will trigger the installation, reconfiguration or removal of the KEDA Controller resource.
Only a resource named `keda` in the namespace where the operator is installed will trigger the installation, reconfiguration or removal of the KEDA Controller resource.

There should be only one KEDA Controller in the cluster.
There should be only one KEDA Controller in the cluster.

The operator will behave in this manner whether it is installed with the `AllNamespaces` or `OwnNamespace` install mode. While the operator more closely matches the `OwnNamespace` semantics, `AllNamespaces` is a supported installation mode to allow it to be installed to namespaces with existing `OperatorGroups` which require that installation mode, such as `openshift-operators`.

0 comments on commit 47da0c9

Please sign in to comment.