-
Notifications
You must be signed in to change notification settings - Fork 820
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
[Doc] Update allocator service & multi-cluster allocation documentation #1802
Conversation
Build Failed 😱 Build Id: e4ee45d9-b6a9-43a5-8bde-c294ac632b4d To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 4314d2ac-4fc4-4dca-9764-f7a682bf7f0b The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Failed 😱 Build Id: 903876fc-76ba-4610-b6d1-d6af28f58afc To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: 6fc9e09b-52a7-4e4f-a758-d376e012b346 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 05b980a3-2f1a-4923-aa58-1ac1fb37a37f The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
|
||
Here is an example of using a self-signed `ClusterIssuer` for configuring allocator-tls `Secret`: | ||
|
||
```bash | ||
#!/bin/bash | ||
# Create a self-signed ClusterIssuer | ||
cat <<EOF | kubectl apply -f - | ||
apiVersion: cert-manager.io/v1alpha2 | ||
apiVersion: cert-manager.io/v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you ack that it is ok to publish these changes for the existing release (vs. gating them on the next agones release)? I think that it should be ok, but want to double check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are ok, unless a cluster is using an old version of cert-manager, which is independent to Agones version.
I manually tested it on Agones v1.6 cluster.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pooneh-m, roberthbailey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: 3b950929-1f5d-4d38-8a92-1de2d5315464 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
And I submitted without getting an ack.... oops. |
Co-authored-by: Alexander Apalikov <[email protected]> Co-authored-by: Robert Bailey <[email protected]>
What type of PR is this?
/kind documentation
What this PR does / Why we need it:
Add a note in the doc for (1) priority number interpretation in multi-cluster; (2) emphasize on configuring cert-manager
certificate
based on the underlying system; (3) prereq for cmd-line tool installation in allocator doc.Which issue(s) this PR fixes:
Closes #1781 and #1582
Special notes for your reviewer: