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

Updating initializer link in README #1386

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Updating initializer link in README #1386

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e728698
Updating initializer link in README
hamza-m-masood Apr 29, 2023
2ed45e5
Merge branch 'master' into patch-2
hamza-m-masood May 3, 2023
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
6 changes: 2 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,12 @@ You can either configure the default kubernetes scheduler to communicate with
stork or launch another instance of kube-scheduler.

### Initializer (Experimental)
If you are not able to update the schedulerName for you applications to use
stork, you can enable the app-initializer feature. This uses the Kubernetes
[AdmissionController Initializer](https://kubernetes.io/docs/admin/extensible-admission-controllers/#initializers)
If you are not able to update the schedulerName for you applications to use stork, you can enable the app-initializer feature. This uses the Kubernetes AdmissionController Initializer
feature to automatically update the scheduler to stork if your application
(deployment or statefulset) is using volumes backed by the configured driver.

To enable the Initializer you need to:
* [Enable the Intializer feature in your Kubernetes cluster](https://kubernetes.io/docs/admin/extensible-admission-controllers/#enable-initializers-alpha-feature)
* [Enable the Intializer feature in your Kubernetes cluster](https://github.com/kelseyhightower/kubernetes-initializer-tutorial)
since it is an alpha feature.
* Add "--app-initializer=true" option to stork (in either the deployment or daemonset spec file)
* Add the [stork-initializer spec](specs/stork-initializer.yaml) to you Kubernetes cluster using `kubectl create -f stork-initializer.yaml`
Expand Down