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

Intro tutorials for MCS API use cases #21

Open
lauralorenz opened this issue Nov 17, 2022 · 3 comments
Open

Intro tutorials for MCS API use cases #21

lauralorenz opened this issue Nov 17, 2022 · 3 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@lauralorenz
Copy link
Contributor

Develop some vendor agnostic intro tutorials about the MCS API that can be easily digested as part of a generic documentation push. Keep them implementation agnostic but I think it would be useful to tie them to some common use cases as suggested below.

Ideas:

  • MCS for a single-cluster stateful service serving multiple clusters (single ServiceExport case) (see this walkthrough for some inspo)
  • MCS for a same-named stateless service in clusters in different regions for simple failover (merged ServiceExport case)
  • MCS for a same-named stateless service for blue-green upgrade (see this video for example)
@lauralorenz
Copy link
Contributor Author

/help
/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@lauralorenz:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

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.

@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Nov 17, 2022
@holgerson97
Copy link

Hi @lauralorenz

I am new to the project and would be happy to take over this part. First I wanted to clarify if this is something that is still needed, let me know what you think!

Kind regards,
Nils

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

3 participants