[Service Catalog]: Pod Preset

[jessfraz]

Description

Add a policy resource that allows loose coupling from services to the pods that consume them.
Proposal here: kubernetes/community#254

Progress Tracker

• 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: [Proposal] Pod Injection Policy community#254
    • Repo: kubernetes/kubernetes
    • Initial API review: [Proposal] Pod Injection Policy community#254
      • Any code that changes an API (/pkg/apis/...)
      • cc @kubernetes/api
    • My Shepherd is: @pmorie
    • My Secondary Contact Point is:@pwittrock
  • 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: Add pod preset docs website#2807
      • 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
• 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
• 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 http://github.com/kubernetes/kubernetes repository,
  and sometimes http://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

• Write user docs and get them merged in.
• User docs go into http://github.com/kubernetes/kubernetes.github.io.
• When the feature has user docs, please add a comment mentioning @kubernetes/docs.
• When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

[idvoretskyi]

@jessfraz can you update this feature request with more details?
Which release does it target, which SIG is responsible for the feature, who is the feature owner?

[jessfraz]

Yes sorry, is there a template for what details go here and what goes into the proposal?

[idvoretskyi]

@jessfraz feel free to update the issue body (the new template is on the way)

[idvoretskyi]

@jessfraz will it be alpha (or beta/stable) for 1.6?

[jessfraz]

we are hoping for alpha

…

On Mon, Feb 27, 2017 at 12:55 PM Ihor Dvoretskyi ***@***.***> wrote: @jessfraz <https://github.com/jessfraz> will it be alpha (or beta/stable) for 1.6? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#162 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYNbB-S4_sQ9qqn1RBInscvC75TDEcdks5rgzhGgaJpZM4LcRTI> .

[pwittrock]

@jessfraz This is likely not landing in 1.6, correct?

[pmorie]

@pwittrock we're hoping to get it into 1.6, yes.

[duglin]

should probably update the text here with the new name

[pwittrock]

Development complete and merged. Documentation in progress.

[devin-donnelly]

The docs PR for this still needs a tech review.

kubernetes/website#2807

[kuroneko25]

Any idea if this is going to hit beta in 1.7?

[idvoretskyi]

@kuroneko25 features and code freeze deadlines are already passed, this feature is not targeting 1.7.

[duglin]

In the sig-arch call yesterday they talked about moving PodPreset to the svc-cat repo and continuing the work over there. Not sure if this will make it for v1.8 or not since it will also require it to use initializers - and see this comment: kubernetes-retired/service-catalog#1041 (comment)

[idvoretskyi]

@duglin @kubernetes/sig-service-catalog-feature-requests is it expected that this feature will be developed in a general Kubernetes scope (following the general timelines etc)?

If not, feel free to close the feature request.

[pwittrock]

PodPreset is going to be moved to the service catalog incubator project.

[Stono]

@pwittrock Sorry for commenting on a closed thread but I'm struggling to find any information when podpreset will be in beta (thus GA on GKE), every thread stream I seem to follow is closed.

Any ideas?

[alexkreidler]

Any updates on this? Are most Kubernetes APIs intended to stay in Alpha for almost 3 years?

I'm not really sure if this feature has the momentum behind it to go into beta, but I know lots of cloud kubernetes environments (EKS, GKE, etc) won't enable it unless it does, and I'm really looking forward to using this feature in a bigger way.

Let me know if anyone is still involved in this feature or if there's anything I can do to help!

[kfox1111]

I just bumped into this feature and it looks to be very useful to me. Whats the plan around this?