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

Attach relevant KEPs to roadmap/vision #1724

Closed
justaugustus opened this issue Oct 11, 2021 · 13 comments · Fixed by #1810
Closed

Attach relevant KEPs to roadmap/vision #1724

justaugustus opened this issue Oct 11, 2021 · 13 comments · Fixed by #1810
Assignees
Labels
area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/release-eng/security Issues or PRs related to release engineering security area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@justaugustus
Copy link
Member

@saschagrunert repeating the question @lachie83 asked on slack here - https://kubernetes.slack.com/archives/C2C40FMNF/p1633713488372400?thread_ts=1633618860.356500&cid=C2C40FMNF

Are you raising KEPs for these deliverables? It looks like a lot of them should require a KEP.

Looks like @PushkarJ thinks @kubernetes/sig-security may be interested as well?

Originally posted by @dims in #1719 (comment)

@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Oct 11, 2021
@justaugustus
Copy link
Member Author

From me in #1719 (comment):

Absolutely! We'll be working on tying all of the threads together with KEPs post-KubeCon. We'll rope in participating SIGs as those drafts get opened. :)

/assign @saschagrunert @justaugustus @cpanato @puerco @jeremyrickard
/milestone v1.23

@justaugustus
Copy link
Member Author

/sig release
/kind design documentation
/area release-eng artifacts release-eng/security security
/milestone v1.23

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. kind/design Categorizes issue or PR as related to design. kind/documentation Categorizes issue or PR as related to documentation. area/release-eng Issues or PRs related to the Release Engineering subproject area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Oct 11, 2021
@k8s-ci-robot
Copy link
Contributor

@justaugustus: The label(s) area/security cannot be applied, because the repository doesn't have them.

In response to this:

/sig release
/kind design documentation
/area release-eng artifacts release-eng/security security
/milestone v1.23

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 the area/release-eng/security Issues or PRs related to release engineering security label Oct 11, 2021
@saschagrunert
Copy link
Member

saschagrunert commented Oct 11, 2021

Makes sense, let's sync up on this after KubeCon.

@MadhavJivrajani
Copy link

/remove-kind design
/kind feature
kind/design is migrated to kind/feature, see kubernetes/community#6144 for more details

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/design Categorizes issue or PR as related to design. labels Oct 11, 2021
@dims
Copy link
Member

dims commented Oct 11, 2021

thanks a ton @justaugustus and @saschagrunert really looking forward to the shape of this.

@dlorenc
Copy link

dlorenc commented Oct 13, 2021

Let me know how I can help out with these! cc @n3wscott offered to help as well.

@saschagrunert
Copy link
Member

As discussed this monday with @puerco, we will outline a first KEP for the SLSA compliance. This KEP will not feature too many technical details, but should act as starting point for follow-ups like "how to sign container images in our release pipeline".

@sftim
Copy link
Contributor

sftim commented Oct 22, 2021

I think I could make time to work on / help with taking one (not all) of these roadmap ideas and starting off the KEP process for them. Copy me in on the relevant issue if someone wants that, or ask in Slack.

@saschagrunert
Copy link
Member

I think I could make time to work on / help with taking one (not all) of these roadmap ideas and starting off the KEP process for them. Copy me in on the relevant issue if someone wants that, or ask in Slack.

Will do, thanks for offering the help @sftim!

@saschagrunert
Copy link
Member

The initial draft of the sining KEP is proposed in kubernetes/enhancements#3061

@saschagrunert
Copy link
Member

@justaugustus when do we consider this one as done?

@justaugustus
Copy link
Member Author

@justaugustus when do we consider this one as done?

I think we should link the KEPs to the roadmap to close this out.
The tracking issues are there for most, but not direct links to KEPs.

Let me know if you have time to get to that. If not, I'll put it on my list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/release-eng/security Issues or PRs related to release engineering security area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants