Skip to content

docs: clarify selector labels behavior #1829

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

Open
KevinSnyderCodes wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify selector labels behavior #1829

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/gitbook/usage/how-it-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,7 @@ In addition to `app`, Flagger supports `name` and `app.kubernetes.io/name` selec
If you use a different convention you can specify your label with the `-selector-labels=my-app-label`
command flag in the Flagger deployment manifest under containers args
or by setting `--set selectorLabels=my-app-label` when installing Flagger with Helm.
Flagger will only use the first matching label it finds from the selector labels.

If the target deployment uses secrets and/or configmaps,
Flagger will create a copy of each object using the `-primary` suffix
Expand Down