-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Issue with k8s.io/docs/home/ Example buttons do not work #16542
Comments
/kind bug |
1.16 is pointing to 3.3.7. Updating it to point to v4.3.1 (https://kubernetes.io/js/bootstrap-4.3.1.min.js )should make these buttons work. |
Yes should work but the change must be made in the api reference generator |
/assign |
@medmedchiheb Thanks for assigning this to yourself! I'm not very familiar with the kubernetes-incubator/reference-docs. Is it possible to point to a CDN instead of updating bootstrap.min.js ? Also, updating reference-docs is the long-term fix. Since the process of generating the API docs is started manually, how do we update the content in kubernetes/website/static/docs/reference/generated/kubernetes-api? |
It's just a quick fix, as you can see from the template. |
/priority backlog |
this is two-fold: 1) update the code in the kubernetes-incubutor/reference-docs project (longterm fix); and 2) update kubernetes/website/static..... See Slack thread |
/remove-priority backlog Updating the current generated API doc index.html is critical because the buttons don't work (see #16263 for v1.15). Long-term fix has already been added to kubernetes-incubator/reference-docs. |
/lifecycle active |
This is a Bug Report
Problem:
The "kubectl example" and "curl example" buttons do not currently work.
Bootstrap fails to load and I'm guessing the toggle for the details panel is handled by that.
Proposed Solution:
Make sure the file is deployed: https://kubernetes.io/js/bootstrap-3.3.7.min.js
or just use a CDN
Page to Update:
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16
Additional Information
The text was updated successfully, but these errors were encountered: