-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
containerize generating k8s reference documentation script #28037
Comments
@PI-Victor: The label(s) In response to this:
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. |
/triage accepted |
Linux 😉 |
/area release-engineering |
@sftim: The label(s) In response to this:
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. |
/area release-engineering |
@sftim: The label(s) In response to this:
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. |
/area release-eng found it! |
No preference from me. |
As we've missed this for v1.22 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/lifecycle frozen |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
Is this issue still relevant? I'd like to help |
Help in this will be very much appreciated @Gauravpadam |
/triage accepted |
@sftim I see some errors on testing the script for While this should not affect our dockerfile, I'd like to know your thoughts on them
|
I don't have much experience generating this documentation, so I don't really have an opinion here @Gauravpadam. We should aim to define a container image and a way to run it so that you get the documentation generated. |
No worries @sftim, I'll figure it out eventually |
Should I just host the image on a public repository? (I'm mentioning the build steps currently) |
The update-imported-docs.py that is used to generate the kubernetes documentation reference should be containerized to make it easier for users that want to update the ref docs.
This container should include all the tooling mentioned in the quickstart.
Q:
OSLinux flavor preferences for the container?Q: Locally buildable Dockerfile or push an already created image to hub.docker.com/quay.io?
Q: Anything else worth mentioning that i've missed
cc @sftim @reylejano @jimangel @irvifa
/assign
/priority important-soon - targeting this change before 1.22 release
The text was updated successfully, but these errors were encountered: