Skip to content

Commit

Permalink
Removes references to OpenShift (it just adds confusion)
Browse files Browse the repository at this point in the history
  • Loading branch information
dougbtv committed Jan 3, 2024
1 parent dc0888c commit e34390d
Showing 1 changed file with 3 additions and 7 deletions.
10 changes: 3 additions & 7 deletions doc/extended-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,8 +136,6 @@ You'll note that in the `ipam` section there's a lot less parameters than are us

## Reconciler Cron Expression configuration for clusters via flatfile (optional)

*NOTE: configuring cron expression prior to cluster launch will only work for **non-Openshift** Kubernetes clusters, such as a vanilla Kubernetes cluster. Skip to the next section if you have an Openshift cluster or a cluster that has already launched.*

You may want to provide a cron expression to configure how frequently the ip-reconciler runs. For clusters that have not yet been launched, this can be configured via the flatfile.

You can speficy the `WHEREABOUTS_RECONCILER_CRON` environment variable in your daemonset definition file to override the default cron expression:
Expand All @@ -149,13 +147,11 @@ You can speficy the `WHEREABOUTS_RECONCILER_CRON` environment variable in your d
## Reconciler Cron Expression Configuration for live clusters via configmap (optional)
You may want to provide a cron expression to configure how frequently the ip-reconciler runs. For **Openshift** Kubernetes clusters, this is done via updating the cron-scheduler-configmap.
You can check that the cron-scheduler-configmap is present by running `oc get configmaps` in the openshift-multus namespace.
You may want to provide a cron expression to configure how frequently the ip-reconciler runs.
To update the cron-scheduler-configmap, run `oc edit configmap cron-scheduler-configmap` and adjust the value to a valid cron expression of your liking. Shortly after, the reconciler schedule will update.
You can check that the cron-scheduler-configmap is present by running `kubectl get configmaps` in the namespace used for Whereabouts.

This comment has been minimized.

Copy link
@maiqueb

maiqueb Jan 3, 2024

Collaborator

the actual name of the config map is whereabouts-config.

This comment has been minimized.

Copy link
@maiqueb

maiqueb Jan 3, 2024

Collaborator

name: whereabouts-config


If you are using a non-Openshift cluster, you can do the same steps, but you will need to look for the configmap in the kube-system namespace.
To update the cron-scheduler-configmap, run `kubectl edit configmap cron-scheduler-configmap` and adjust the value to a valid cron expression of your liking. Shortly after, the reconciler schedule will update.

This comment has been minimized.

Copy link
@maiqueb

maiqueb Jan 3, 2024

Collaborator

the actual name of the config map is whereabouts-config.

This comment has been minimized.

Copy link
@maiqueb

maiqueb Jan 3, 2024

Collaborator

name: whereabouts-config


## Installing etcd. (optional)

Expand Down

0 comments on commit e34390d

Please sign in to comment.