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.

Sign up for GitHub

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

Jump to bottom

Local deployment minor fix #603

Merged
merged 1 commit into from
Feb 3, 2020
Merged

Local deployment minor fix #603

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,6 @@ To be KEDA to be fully operational we need to deploy Metrics Server first.

1. Deploy CRDs and KEDA into `keda` namespace
```bash
kubectl create namespace keda
kubectl apply -f deploy/crds/keda.k8s.io_scaledobjects_crd.yaml
kubectl apply -f deploy/crds/keda.k8s.io_triggerauthentications_crd.yaml
kubectl apply -f deploy/
Expand All @@ -111,9 +110,9 @@ To be KEDA to be fully operational we need to deploy Metrics Server first.
```bash
kubectl scale deployment/keda-operator --replicas=0 -n keda
```
3. Run the operator locally with the default Kubernetes config file present at `$HOME/.kube/config`
3. Run the operator locally with the default Kubernetes config file present at `$HOME/.kube/config` and change the operator log level via `--zap-level=` if needed
```bash
operator-sdk run --local --namespace=""
operator-sdk run --local --namespace="" --operator-flags="--zap-level=info"
```
> Note: On older operator-sdk versions you need to use command `up` instead of `run`.

Expand Down