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.

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

Update Canary Testing Documentation #3760

Merged
merged 6 commits into from
Apr 16, 2024
Merged
Changes from all commits
Commits
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
9 changes: 4 additions & 5 deletions site/content/en/docs/Integration Patterns/canary-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,14 @@ To ensure we don't have to change the Allocation system every time we have a can
state that in our system, the label `canary: "true"` will be added to any canary `Fleet` in the cluster.

```yaml
apiVersion: "allocation.agones.dev/v1"
apiVersion: allocation.agones.dev/v1
kind: GameServerAllocation
spec:
preferred:
selectors:
- matchLabels:
canary: "true"
required:
matchLabels:
agones.dev/fleet: stable
- matchLabels:
agones.dev/fleet: stable
```

The above `Allocation` will then preferentially choose the `Fleet` that has `GameServers` with the label and key
Expand Down
Loading