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 1 commit
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
15 changes: 10 additions & 5 deletions site/content/en/docs/Integration Patterns/canary-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,12 +35,17 @@ state that in our system, the label `canary: "true"` will be added to any canary
apiVersion: "allocation.agones.dev/v1"
kind: GameServerAllocation
spec:
preferred:
- matchLabels:
canary: "true"
required:
matchLabels:
- matchLabels:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@markmandel do you have any preference on if this examples uses the labels canary: "true" canary: "false" or agones.dev/fleet: green-fleet agones.dev/fleet: blue-fleet?

   selectors: 
     - matchLabels:
         canary: "true"
         agones.dev/fleet: green-fleet

canary: "true"
agones.dev/fleet: stable
players:
Kalaiselvi84 marked this conversation as resolved.
Show resolved Hide resolved
minAvailable: 0
maxAvailable: 99
- matchLabels:
agones.dev/fleet: stable
players:
minAvailable: 0
maxAvailable: 99
```

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