Fixes bootstrap js ref to 4.3.1 for API v1.15

[ahlinc]

A fix for the v1.15 API version was missed in the #14775 PR
because the dev-1.15 branch was forked from the master branch
before the fix and has been merged back to the master after it.

[k8s-ci-robot]

Welcome @ahlinc!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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. I understand the commands that are listed here.

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit ce039e7

https://deploy-preview-16263--kubernetes-io-master-staging.netlify.com

[ahlinc]

/assign @tfogo

[ahlinc]

/cc @Bradamant3 @jimangel @kbarnard10 @pwittrock @steveperry-53 @tengqm @zacharysarah @zparnold Could someone review, merge and deploy this fix because it's related to the API reference for the latest v1.15 k8s version and fixes broken example buttons on the API page?
Thanks.

[zacharysarah]

@ahlinc 👋 Thanks for this fix. This page is the downstream result of an upstream process; so if you only fix it here, changes will be overwritten the next time we generate the reference.

Please work with @tengqm and @aimeeu to find the correct location for the upstream source fix.

[ahlinc]

@zacharysarah thank you for looking to this PR. As I found upstream already is totally fine and only this specific already generated page requires direct fix in the same way as it was done in mentioned #14775 PR. Please correct me if I'm wrong, as I found version specific API references placed in a static/docs/reference/generated/kubernetes-api folder are stored in pregenerated form so there is no impact on them from upstream changes and the generation process just copies versioned API reference folders from a static/ into a public/ folder as is without any changes in the same way like when we run make docker-build locally.

[zacharysarah]

@ahlinc Sounds good to me. Thanks for the explanation.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zacharysarah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zacharysarah]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ahlinc]

@zacharysarah Awesome, thank you, now the page works correctly.