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

Updates to the HA document #3599

Merged
merged 1 commit into from
Dec 8, 2020
Merged

Updates to the HA document #3599

merged 1 commit into from
Dec 8, 2020

Conversation

qu1queee
Copy link
Contributor

@qu1queee qu1queee commented Dec 4, 2020

Changes

Enhance enabling-ha.md doc

In addition, categorize the changes you're making using the "/kind" Prow command, example:

/kind documentation

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

Update enabling-ha.md document, to highlight the usage of buckets for the HA solution in the pipeline controller.

@tekton-robot tekton-robot added kind/documentation Categorizes issue or PR as related to documentation. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Dec 4, 2020
@tekton-robot tekton-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 4, 2020
@tekton-robot
Copy link
Collaborator

Hi @qu1queee. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@qu1queee
Copy link
Contributor Author

qu1queee commented Dec 4, 2020

@afrittoli fyi

@afrittoli
Copy link
Member

/ok-to-test

@tekton-robot tekton-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesnt merit a release note. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Dec 4, 2020
@afrittoli
Copy link
Member

@qu1queee it looks like you dropped the release part from the PR template, I added it back with no release notes, feel free to change it if you want to provide release notes

@ghost
Copy link

ghost commented Dec 4, 2020

/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbwsg

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesnt merit a release note. labels Dec 4, 2020
@qu1queee
Copy link
Contributor Author

qu1queee commented Dec 7, 2020

@afrittoli thanks, I did add a sentence for the release notes.

Copy link
Member

@jerop jerop left a comment

Choose a reason for hiding this comment

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

@qu1queee could you please squash your commits? we want to have 1 commit per PR as described in https://github.com/tektoncd/community/blob/master/standards.md#commits

This document was missing the `data.buckets` configurable parameter
for the leader election.

Remove references to `data.resourceLock` for HA config

While enhancing the HA document, we realized that the `resourceLock``
field is not configurable in the Knative side, but rather hardcoded.

You can see in https://github.com/knative/pkg/blob/master/leaderelection/config.go#L74-L87
, where the Config object is defined, that this field is not included.
Also, the value for it seems to be hardcoded to "leases", as seen in
https://github.com/knative/pkg/blob/master/leaderelection/config.go#L38

Signed-off-by: Zoe <xigxjn@cn.ibm.com>
@qu1queee qu1queee requested a review from jerop December 7, 2020 16:22
@qu1queee
Copy link
Contributor Author

qu1queee commented Dec 7, 2020

@jerop make sense, done

@dlorenc
Copy link
Contributor

dlorenc commented Dec 8, 2020

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2020
@tekton-robot tekton-robot merged commit 705e971 into tektoncd:master Dec 8, 2020
@qu1queee qu1queee deleted the ha_docs_update branch December 8, 2020 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants