Update install.md to include alpine 3.19 #93
Conversation
* Update deploy-with-kic.md * Update deploy-with-kic.md --------- Co-authored-by: Alan Dooley <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
* feat: Update pull request template This commit fixes the spacing issue of the pull request checklist by changing the final checklist item. The relevant information now exists as a sentence after the list, as well as an additional line. The additional line, alongside a similar one added to the checklist, direct the reader to our style guide to review specific guidance that would otherwise be too verbose to add to the template.
* linkchecker update ignore list * update links to kic docs
With the newly open source documentation repository, we can now consolidate all NGINX documentation into one place. This has a lots of benefits which include but are not limited to more effective content re-use, pipeline engineering and style enforcement. This commit adds all of the content for NGINX Gateway Fabric, and updates all relevant folder and file names, including link references. Once this content has been successfully deployed, a PR to remove all documentation traces and tooling will be opened in the Gateway Fabric repository, decoupling the documentation fully. It also updates the frontmatter of every single page in the documentation set. They are now all consistent in their fields and formatting, and a handful of IA or heading changes have been made as low-hanging fruit to bring the documentation set closer to full consistency.
alpine 3.19 doc
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
✅ Deploy Preview will be available once build job completes!
|
add alpine 3.19 sections
…ses" (#91) * Add log monitoring examples and guidance to "About subscription licenses" * added log warnings to include
|
recheck |
|
@ohad-perets This is the incorrect branch for the change: please change your target to |
|
I have hereby read the F5 CLA and agree to its terms |
|
recheck |
but we need the changes for both, 4.13 & 5.5 why do we need 2 separate branches? |
There might have been separate changes for each individual release: there is a release branch for each individual product's versions. If NAP releases are always going to be tied together despite separate versioning, we'll just use a single one going forward. |
|
new PR will be sent shortly |
alpine 3.19 doc
Proposed changes
adding doc for alpine 3.19(identical to other alpine OS)
Testing: preview & team review
If this PR addresses an issue on GitHub, ensure that you link to it here:
Closes https://jira.f5net.com/browse/WAFMC-9431
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.md)Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation.
Please refer to our style guide for guidance about placeholder content.