jiebi/CodeConvo huggingface dataset:
I'd see that as valuable in the conceptualization of step 2. Once we figure out solid vizualizations for concepts with some quick accompanying sketches, creating effective symbols / icons is mostly a matter of applying sound visual design. As far as getting that conversation started, how would you recommend going about that? I can just create a new issue with of concepts needing diagrams and give people a chance to chime in?
Creating a new issue sounds good. As part of the issue, we probably want to figure out what things we will need symbols / icons to represent, and what things will need diagrams composed of multiple symbols. What sort of things do we still need / want folks to give feedback on? The list of digram topics? How the concepts are represented in diagrams? Main concepts we want to convey? Diagrams for processes vs concepts?
I found this issue looking for kubernetes diagram symbols and tried following through to other linked to issues to find if there was ever a set of diagram symbols bundled together for kubernetes components but could not find them. Has this happened? If so, where can they be found? Thanks!
unfortunately there is no standardized set of symbols. This specific issue's effort sort of fizzled out and no one's yet initiated another attempt. If you have any ideas of a good approach please share! I'd love to enable more visualization of concepts.
see kubernetes/kubernetes.
Outcome of kubernetes/kubernetes
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: describes the API List Chunking feature. However, this is a beta feature. Proposed Solution: Warn readers that this feature is not yet stable, using a Hugo shortcode. You can look up when the feature went beta from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 /sig api-machinery
/assign
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Document the EndpointSlice controller ignores nodes with the following labels or Proposed Solution: Document labels Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind cleanup /language en
/assign
/sig network /triage accepted
This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: ref. Japanese Localization document: /area localization /language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This is a Bug Report Problem: Using as an example, Note blocks that start with a bullet appear malformed, same outcome in both Chrome and Safari, note the dot over the e characters and incorrect indentation - <img width="723" alt="image" src=""Proposed Solution: Let's discuss further, possibly, maybe this can be fixed via hugo, otherwise we could investigate an update to all affected pages. Page to Update: We should update all notes that meet this criteria, investigate after a proposed solution is agreed.
/area web-development
It seems that our recent update to align with Docsy-style callouts in may have unintentionally caused this issue. There's definitely room for improvement here, and we should address this to ensure the content is displayed properly. /priority backlog /triage accepted
Oops. I think we can address this with a CSS fix; for example, not making the “note” text an inline block when the parent contains either or (using and selectors). For a simple fix, make the “Note:” text never be an inline block.
i would like to try
/assign
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In the , under redirects to a topic that has been removed in release 1.30 by this PR Therefore, the hyperlink no longer exists. was replaced with Proposed Solution: Replace this line in with this line and adding a hyperlink for Specifying Apparmor Confinement: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--If the suggested solution is okay. I can raise a PR for it.
/assign /sig node /language en /sig docs
/triage accepted /priority backlog
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Using chrome (120.0.6099.129 (Official Build) (x86_64)) on macOS (12.7.1 (21G920)) and hitting the link from the , I hit the documentation for Kubernetes 1.29 and I can only see the navigation with the list of objects. <img width="1595" alt="image" src=""I have observed the same problem on safari ( 17.1.2 (.2.9.11.12, )): <img width="1587" alt="image" src=""And Firefox (121.0 (64-bit)): <img width="1266" alt="image" src=""Proposed Solution: Get the content back as in the : <img width="1585" alt="image" src=""Page to Update:
/retitle One-page API reference missing for Kubernetes v1.29
The API reference for v1.29 was successfully generated in PR , as evidenced by the verified information in the . It appears that we're encountering a rendering glitch.
Upon further investigation, it seems that the page data isn't rendering correctly in dark mode (sort of). I switched my device/browser theme to light mode, and the page info became visible (Refer below screenshot). It seems like there might be some missing CSS and scripts causing this issue. <img width="1278" alt="api-refence-light-mode" src=""
This is definitely something we should address. (cc: /triage accepted
/retitle Content of 'One-page API Reference for v1.29' not rendering properly in dark mode
/assign
The original description of the issue is proper and correct, I don't know why you are so akin to change these issue descriptions. I'm raising this question because when an issue title is changed, my email client won't treat the issues as the same one. The "conversation" mode no longer works. I'm receiving emails for every comment as a separate email. It is not a big deal but it is really annoying.
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This reads a little unclear: kube-scheduler kube-scheduler watches newly created pods that have no node assigned, and selects a node for them to run on. Proposed Solution: kube-scheduler kube-scheduler watches for newly created pods that are not assigned to any node, and selects a node for them to run on. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign