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

Federated Ingress for GCP #82

Closed
22 tasks
ghost opened this issue Aug 25, 2016 · 7 comments
Closed
22 tasks

Federated Ingress for GCP #82

ghost opened this issue Aug 25, 2016 · 7 comments
Assignees
Labels
sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Milestone

Comments

@ghost
Copy link

ghost commented Aug 25, 2016

Description

Add description here

Progress Tracker

  • Before Alpha
    • Write and maintain draft quality doc
      • During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK
    • Design Approval
      • Design Proposal. This goes under docs/proposals. Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation. Paste link to merged design proposal here: PROPOSAL-NUMBER
      • Initial API review (if API). Maybe same PR as design doc. PR-NUMBER
        • Any code that changes an API (/pkg/apis/...)
        • cc @kubernetes/api
      • Identify shepherd (your SIG lead and/or [email protected] will be able to help you). My Shepherd is: [email protected] (and/or GH Handle)
        • A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
        • The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.
      • Identify secondary/backup contact point. My Secondary Contact Point is: [email protected] (and/or GH Handle)
    • Write (code + tests + docs) then get them merged. ALL-PR-NUMBERS
      • Code needs to be disabled by default. Verified by code OWNERS
      • Minimal testing
      • Minimal docs
        • cc @kubernetes/docs on docs PR
        • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
        • New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io
      • Update release notes
  • Before Beta
    • Testing is sufficient for beta
    • User docs with tutorials
      • Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
      • cc @kubernetes/docs on docs PR
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
    • Thorough API review
      • cc @kubernetes/api
  • Before Stable
    • docs/proposals/foo.md moved to docs/design/foo.md
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
    • Soak, load testing
    • detailed user docs and examples
      • cc @kubernetes/docs
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT

More advice:

Design

  • Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

  • Use as many PRs as you need. Write tests in the same or different PRs, as is convenient for you.
  • As each PR is merged, add a comment to this issue referencing the PRs. Code goes in the https://github.com/kubernetes/kubernetes repository,
    and sometimes https://github.com/kubernetes/contrib, or other repos.
  • When you are done with the code, apply the "code-complete" label.
  • When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
    check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
    testing. They won't do detailed code review: that already happened when your PRs were reviewed.
    When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

@ghost ghost added sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. beta-in-1.4 labels Aug 25, 2016
@ghost ghost added this to the v1.4 milestone Aug 25, 2016
@ghost ghost self-assigned this Aug 25, 2016
@janetkuo
Copy link
Member

janetkuo commented Sep 2, 2016

@quinton-hoole Are the docs ready? Please update the docs in https://github.com/kubernetes/kubernetes.github.io, and then add PR numbers and check the docs box in the issue description

@ghost
Copy link
Author

ghost commented Sep 2, 2016

Docs are being written. Should be done next week.

On Fri, Sep 2, 2016 at 11:34 AM, Janet Kuo [email protected] wrote:

@quinton-hoole https://github.com/quinton-hoole Are the docs ready?
Please update the docs in https://github.com/kubernetes/
kubernetes.github.io, and then add PR numbers and check the docs box in
the issue description


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#82 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6NAYxpVhiAWiYkbHlRBNiQRzX9sJwqks5qmGwegaJpZM4JtiRN
.

@jaredbhatti
Copy link

@quinton-hoole Thanks for the heads up.

@jaredbhatti
Copy link

@quinton-hoole Can you add the docs PR to this issue when it's ready to review?

@ghost ghost assigned nikhiljindal and ghost and unassigned ghost Sep 7, 2016
@jaredbhatti
Copy link

@nikhiljindal Another ping on docs. Any PRs you can point me to?

@nikhiljindal
Copy link

Filed kubernetes/website#1215 for all federation docs

@ghost
Copy link
Author

ghost commented Sep 30, 2016

Released alpha in v1.4

@ghost ghost closed this as completed Sep 30, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Projects
None yet
Development

No branches or pull requests

4 participants