Skip to content

Commit

Permalink
remove unnecessary kubernetes/informer references
Browse files Browse the repository at this point in the history
  • Loading branch information
mherwig committed May 2, 2024
1 parent b3ce5d8 commit a499fb0
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 13 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Horizon's Starlight provides a REST endpoint allowing event providers to publish
For the optimal setup, ensure you have:

- A running instance of Kafka
- Access to a Kubernetes cluster on which the `Subscription` (subscriber.horizon.telekom.de) custom resource definition has been registered
- A running instance of Horizon's config server (codename: Quasar)

## Building Starlight

Expand Down Expand Up @@ -90,8 +90,8 @@ oidc:
## Running Starlight
### Locally
Before you can run Starlight locally you must have a running instance of Kafka locally or forwarded from a remote cluster.
Additionally, you need to have a Kubernetes config at `${user.home}/.kube/config.main` that points to the cluster you want to use.
Before you can run Starlight locally you must have a running instance of Kafka locally or forwarded from a remote cluster.
Additionally, you need to have a running instance of Horizon's config server locally (codename: Quasar).
After that you can run Starlight in a dev mode using this command:
```shell
Expand Down
10 changes: 0 additions & 10 deletions src/main/resources/application.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -43,16 +43,6 @@ management:
sampling:
probability: ${ZIPKIN_SAMPLER_PROBABILITY:1.0}

kubernetes:
enabled: true
#roverToken:
#kubeConfigPath:
informer:
resyncperiod:
# 10 minutes
ms: 600000
namespace: ${STARLIGHT_INFORMER_NAMESPACE:playground}

starlight:
features:
publisherCheck: ${STARLIGHT_FEATURE_PUBLISHER_CHECK:true}
Expand Down

0 comments on commit a499fb0

Please sign in to comment.