Skip to content

Commit 6f9a8a8

Browse files
authored
Remove ca-notes (#38)
* lab5 diagram/icons * lab5 graphics * lab5 graphics * add redis and headless * add redis and headless * fix keepalive * lab3 fixes * repo files updated * new readme * lab0 initial * lab0 initial * removed ca-notes * lab9 screenshots * lab9 screenshots
1 parent fe622c4 commit 6f9a8a8

34 files changed

+1144
-364
lines changed

.gitignore

+2-1
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,5 @@ Thumbs.db
1919

2020
# Misc Dir #
2121
############
22-
.apc/
22+
.apc/
23+
lab/kubernetes-ingress

CHANGELOG.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Changelog
22

3-
## 1.0.0 (Month Date, Year)
3+
## 1.0.0 (April 1, 2024)
44

5-
Initial release of the NGINX template repository.
5+
Initial release of the NGINXaaS for Azure Workshop.

CONTRIBUTING.md

+2-26
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,6 @@ The following is a set of guidelines for contributing to this project. We really
88

99
[Contributing](#contributing)
1010

11-
[Code Guidelines](#code-guidelines)
12-
1311
[Code of Conduct](https://github.com/nginxinc/nginx-azure-workshops/blob/main/CODE_OF_CONDUCT.md)
1412

1513
## Getting Started
@@ -24,28 +22,6 @@ Follow our [Getting Started Guide](https://github.com/nginxinc/nginx-azure-works
2422

2523
To report a bug, open an issue on GitHub with the label `bug` using the available bug report issue template. Please ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using our [security policy](https://github.com/nginxinc/nginx-azure-workshops/blob/main/SECURITY.md).**
2624

27-
### Suggest a Feature or Enhancement
28-
29-
To suggest a feature or enhancement, please create an issue on GitHub with the label `enhancement` using the available [feature request template](https://github.com/nginxinc/nginx-azure-workshops/blob/main/.github/feature_request_template.md). Please ensure the feature or enhancement has not already been suggested.
30-
31-
### Open a Pull Request
32-
33-
- Fork the repo, create a branch, implement your changes, add any relevant tests, submit a PR when your changes are **tested** and ready for review.
34-
- Fill in [our pull request template](https://github.com/nginxinc/nginx-azure-workshops/blob/main/.github/pull_request_template.md).
35-
36-
Note: if you'd like to implement a new feature, please consider creating a [feature request issue](https://github.com/nginxinc/nginx-azure-workshops/blob/main/.github/feature_request_template.md) first to start a discussion about the feature.
37-
38-
## Code Guidelines
39-
40-
<!-- ### Go/Python/Bash/etc... Guidelines (OPTIONAL) -->
41-
42-
### Git Guidelines
25+
### Provide Feedback on a Lab Exercise
4326

44-
- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR.
45-
- If possible and/or relevant, use the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format when writing a commit message, so that changelogs can be automatically generated
46-
- Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/> and summarised in the next few points:
47-
- In the subject line, use the present tense ("Add feature" not "Added feature").
48-
- In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
49-
- Limit the subject line to 72 characters or less.
50-
- Reference issues and pull requests liberally after the subject line.
51-
- Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in your text editor to write a good message instead of `git commit -am`).
27+
To send us feedback, please create an issue on GitHub with the label `feedback` using the available feedback template.

README.md

+66-40
Original file line numberDiff line numberDiff line change
@@ -3,66 +3,92 @@
33
[![Community Support](https://badgen.net/badge/support/community/cyan?icon=awesome)](https://github.com/nginxinc/template-repository/blob/main/SUPPORT.md)
44
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](https://github.com/nginxinc/template-repository/main/CODE_OF_CONDUCT.md)
55

6-
# NGINX Template Repository
6+
## github.com/nginxinc/nginx_azure_workshops
77

8-
## What is included on this template?
8+
[![Project Status: Concept – Minimal or no implementation has been done yet, or the repository is only intended to be a limited example, demo, or proof-of-concept.](https://www.repostatus.org/badges/latest/concept.svg)](https://www.repostatus.org/#concept)
9+
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/nginxinc/nginx-azure-workshops/badge)](https://securityscorecards.dev/viewer/?uri=github.com/nginxinc/nginx-azure-workshops)
10+
[![Community Support](https://badgen.net/badge/support/community/cyan?icon=awesome)](https://github.com/nginxinc/nginx-azure-workshops/blob/main/SUPPORT.md) [![Commercial Support](https://badgen.net/badge/support/commercial/cyan?icon=awesome)](http://support.f5.com)
11+
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](https://github.com/nginxinc/nginx-azure-workshops/main/CODE_OF_CONDUCT.md)
912

10-
This template includes all the scaffolding you need to get started on an OSS repository that meets the required NGINX criteria:
13+
<br/>
1114

12-
- [Apache License 2.0](https://github.com/nginxinc/template-repository/blob/main/LICENSE) (required for all NGINX OSS projects)
13-
- [`.gitignore`](https://github.com/nginxinc/template-repository/blob/main/.gitignore) with some minimal sensible defaults
14-
- [Issue](https://github.com/nginxinc/template-repository/blob/main/.github/ISSUE_TEMPLATE) and [PR](https://github.com/nginxinc/template-repository/blob/main/pull_request_template.md) templates
15-
- [Contributing](https://github.com/nginxinc/template-repository/blob/main/CONTRIBUTING.md) guidelines
16-
- [Support](https://github.com/nginxinc/template-repository/blob/main/SUPPORT.md) guidelines for either community and/or commercial support
17-
- [Security](https://github.com/nginxinc/template-repository/blob/main/SECURITY.md) guidelines for reporting major vulnerabilities
18-
- [Code of Conduct](https://github.com/nginxinc/template-repository/blob/main/CODE_OF_CONDUCT.md)
19-
- Open Source Security Foundation (OSSF) Scorecard [(implemented via a GitHub Action)](https://github.com/nginxinc/template-repository/blob/main/.github/workflows/ossf_scorecard.yml)
20-
- [README](https://github.com/nginxinc/template-repository/blob/main/README.md) placeholder. How you structure the README is up to you (although the template provides placeholder sections), but you will need to include:
21-
- A [repostatus](https://www.repostatus.org/) badge
22-
- An OSSF Scorecard badge. (Optional -- Some projects will by their nature have low scores. In such a case you might want to remove this badge!)
23-
- A community and/or commercial support badge. Include the latter -- and replace the commented out badge/URL placeholder with the relevant support URL -- if this repository contains a commercially supported project. You can find a commented out example below the community badge in this README.
24-
- A contributor covenant/code of conduct badge. (Optional -- If you already have multiple badges and want to reduce clutter, simply including the actual code of conduct is enough!)
25-
- An explicit link back to the [Apache License 2.0](https://github.com/nginxinc/template-repository/blob/main/LICENSE)
26-
- An up to date copyright notice
27-
- [Changelog](https://github.com/nginxinc/template-repository/blob/main/CHANGELOG.md) placeholder. (Optional -- A changelog is recommended, but it is not required and can diverge in format from the placeholder here included.)
28-
- [Codeowners](https://github.com/nginxinc/template-repository/blob/main/.github/CODEOWNERS) placeholder. (Optional -- Codeowners is a useful feature, but not all repositories require them.)
15+
# NGINXaaS for Azure Workshop 301
2916

30-
**Note:** If you created a public repository before this template became available (or you didn't know about it's existence), please include any missing files found here in your repository. There is no need if you have a private repository, but we still recommend you include all of the above scaffolding should the repository ever become public.
17+
![](labs/media/nginx-azure-icon.png)
3118

32-
## How do I use this template?
19+
<br/>
3320

34-
**DO NOT FORK** -- this template is meant to be used from the **[`Use this template`](https://github.com/nginxinc/template-repository/generate)** feature.
21+
This Repo is for learning **`NGINX as a Service in Azure`**, with Instructor Lead and Hands-on Lab Exercises and Lab Guides that will teach a student using real world scenarios for using NGINX in front of Azure Resources.
3522

36-
1. Click on **[`Use this template`](https://github.com/nginxinc/template-repository/generate)**
37-
2. Give a name to your project
38-
3. Wait until the first run of CI finishes (GitHub Actions will process the template and commit to your new repo)
39-
4. Clone your new project and tweak any of the placeholders if necessary. Pay special attention to the README!
40-
5. Happy coding!
23+
<br>
4124

42-
**NOTE**: **WAIT** until the first CI run on GitHub Actions finishes before cloning your new project.
25+
**This is an Advanced, 300 Level Workshop.**
4326

44-
---
27+
## Audience
4528

46-
<!-- DELETE THE LINES ABOVE THIS AND WRITE YOUR PROJECT README BELOW -- PLACEHOLDER SECTIONS HAVE BEEN INCLUDED FOR YOUR CONVENIENCE -->
29+
This Workshop is meant for Cloud and Application Architects, Modern Application Developers, DevOps, Platform Ops, and SRE engineers working with NGINX, Azure, Docker, Kubernetes and Ingress Controllers, to learn and understand how NGINX for Azure works - how it is configured, deployed, monitored and managed. Using various Azure Resources like VMs, containers, AKS Clusters, and Azure networking, you will deploy real applications for external access using Nginx for Azure.
4730

48-
[![Project Status: Concept – Minimal or no implementation has been done yet, or the repository is only intended to be a limited example, demo, or proof-of-concept.](https://www.repostatus.org/badges/latest/concept.svg)](https://www.repostatus.org/#concept)
49-
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/nginxinc/nginx-azure-workshops/badge)](https://securityscorecards.dev/viewer/?uri=github.com/nginxinc/nginx-azure-workshops)
50-
[![Community Support](https://badgen.net/badge/support/community/cyan?icon=awesome)](https://github.com/nginxinc/nginx-azure-workshops/blob/main/SUPPORT.md) <!-- [![Commercial Support](https://badgen.net/badge/support/commercial/cyan?icon=awesome)](<Insert URL>) -->
51-
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](https://github.com/nginxinc/nginx-azure-workshops/main/CODE_OF_CONDUCT.md)
31+
`The Student taking this Advanced Workshop must have intermediate skills and knowledge with the following:`
32+
33+
- Azure Cloud, Portal and Azure CLI
34+
- NGINX Webserver, Reverse Proxy, Load Balancing
35+
- NGINX Ingress Controller
36+
- Kubernetes Administration
37+
- Redis In Memory Cache and Redis Tools
38+
- TCP, HTTP/S, DNS, Redis protocols and traffic
39+
- Chrome or browser diagnostic tools
40+
- Linux OS commands and tools
41+
- Container / Docker administration
42+
- Visual Studio Code
43+
44+
You should be proficient with the following technologies and concepts.
45+
46+
- Nginx Webserver and Reverse Proxy
47+
- Nginx Ingress Controller
48+
- Kubernetes; nodes, pods, deployments, services, ingress, nodeport
49+
- Azure Cloud; subscriptions, networking, VMs, AKS Clusters
50+
- Various Desktop tools; Visual Studio, Linux, Terminal, Chrome
51+
52+
<br/>
5253

53-
# nginx_azure_workshops
54+
## Knowledge and Skills Requirements
5455

55-
## Requirements
56+
<br/>
5657

57-
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam elit turpis, varius et arcu elementum, viverra rhoncus sem. Aliquam nec sodales magna, et egestas enim. Mauris lobortis ultrices euismod. Pellentesque in arcu lacus. Mauris cursus laoreet nulla, ac vehicula est. Vestibulum eu mauris quis lorem consectetur aliquam ac nec quam. Vestibulum commodo pharetra mi, at bibendum neque faucibus ut. Mauris et tortor sed sem consectetur eleifend ut non magna. Praesent feugiat placerat nibh, varius viverra orci bibendum sed. Vestibulum dapibus ex ut pulvinar facilisis. Quisque sodales enim et augue tempor mattis. Suspendisse finibus congue felis, ac blandit ligula. Praesent condimentum ultrices odio quis semper. Nunc ultrices, nibh quis mattis pellentesque, elit nulla bibendum felis, quis dapibus erat turpis ac urna.
58+
NGINXaaS for Azure | Hands-On Labs
59+
:-------------------------:|:-------------------------:
60+
![](labs/media/nginx-azure-icon.png) | ![](labs/media/developer-seated.svg)
61+
62+
<br/>
63+
64+
To meet the Prerequisite skills requirement, there are other Workshops from Nginx and Azure Learning to help you prepare. The student must have completed the previous two Nginx Workshops, prior to taking this workshop. (Or have equivalent knowledge).
65+
66+
- Nginx Basics Workshop - 101 (https://github.com/nginxinc/nginx-basics-workshops/tree/master/labs)
67+
- Nginx Plus Ingress Workshop - 201 (https://github.com/nginxinc/nginx-ingress-workshops/tree/main/Plus/labs)
68+
- Azure Portal and AzureCLI training from Microsoft Learn (https://learn.microsoft.com/en-us/training/azure/)
69+
70+
See [Lab0 Readme](/labs/lab0/readme.md) for the Hardware/Software and Skills Prerequisites for taking this Workshop and completing the Lab Exercises.
71+
72+
<br/>
5873

5974
## Getting Started
6075

61-
Duis sit amet sapien vel velit ornare vulputate. Nulla rutrum euismod risus ac efficitur. Curabitur in sagittis elit, a semper leo. Suspendisse malesuada aliquam velit, eu suscipit lorem vehicula at. Proin turpis lacus, semper in placerat in, accumsan non ipsum. Cras euismod, elit eget pretium laoreet, tortor nulla finibus tortor, nec hendrerit elit turpis ut eros. Quisque congue nisi id mauris molestie, eu condimentum dolor rutrum. Nullam eleifend elit ac lobortis tristique. Pellentesque nec tellus non mauris aliquet commodo a eu elit. Ut at feugiat metus, at tristique mauris. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae;
76+
Review the Github Repo content for the Nginx Basics and Nginx Plus Ingress Workshops. If you have taken these Workshops, and understand the content, you can successfully complete the Lab exercises in this Nginx for Azure Workshop. It is HIGHLY recommended that you complete the 101 and 201 Workshops prior.
77+
78+
It is HIGHLY recommended that you complete Azure Training from http://learn.microsoft.com, so you are familiar with Azure Portal, menus, and various resources and components.
79+
80+
It will take approximately 4 hours to complete the Nginx for Azure Workshop.
81+
82+
<br/>
6283

6384
## How to Use
6485

65-
Maecenas at vehicula justo. Suspendisse posuere elementum elit vel posuere. Etiam quis pulvinar massa. Integer tempor semper risus, vitae maximus eros ullamcorper vitae. In egestas, ex vitae gravida sodales, ipsum dolor varius est, et cursus lorem dui a mi. Morbi faucibus ut nisi id faucibus. Sed quis ullamcorper ex. In et dolor id nunc interdum suscipit.
86+
The content and lab exercises are presented in a sequence as you build and add additional Nginx and Azure features and functionality as you progress. It is essential that the Lab Exercises are completed in the order provided. This content provided is for example only, is not for production workloads. The user of this information assumes all risks.
87+
88+
- Click [LabGuide](/labs/LabGuide.md) to begin the Lab Exercises.
89+
- Click [Lab0 Readme](/labs/lab0/readme.md) to review the Lab0 Prerequisites - "Know before you Go".
90+
91+
<br/>
6692

6793
## Contributing
6894

SECURITY.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22

33
## Latest Versions
44

5-
We advise users to run or update to the most recent release of this project. Older versions of this project may not have all enhancements and/or bug fixes applied to them.
5+
We advise users to run the most recent release of the nginx_azure_workshops. Older versions of the nginx_azure_workshops may not have all enhancements and/or bug fixes applied to them.
66

77
## Reporting a Vulnerability
88

99
The F5 Security Incident Response Team (F5 SIRT) has an email alias that makes it easy to report potential security vulnerabilities.
1010

1111
- If you’re an F5 customer with an active support contract, please contact [F5 Technical Support](https://www.f5.com/services/support).
12-
- If you aren’t an F5 customer, please report any potential or current instances of security vulnerabilities with any F5 product to the F5 Security Incident Response Team at [email protected]
12+
- If you aren’t an F5 customer, please report any potential or current instances of security vulnerabilities with any F5 product to the F5 Security Incident Response Team at [email protected].
1313

1414
For more information visit [https://www.f5.com/services/support/report-a-vulnerability](https://www.f5.com/services/support/report-a-vulnerability)

SUPPORT.md

+29-7
Original file line numberDiff line numberDiff line change
@@ -4,34 +4,56 @@
44

55
We use GitHub for tracking bugs and feature requests related to this project.
66

7-
Don't know how something in this project works? Curious if this project can achieve your desired functionality? Please open an issue on GitHub with the label `question`.
7+
Don't know how something in the nginx_azure_workshops works? Curious if the nginx_azure_workshops can achieve your desired functionality? Please open an issue on GitHub with the label `question`.
8+
9+
<br/>
810

911
## NGINX Specific Questions and/or Issues
1012

1113
This isn't the right place to get support for NGINX specific questions, but the following resources are available below. Thanks for your understanding!
1214

13-
### Community Slack
15+
<br/>
1416

15-
We have a community [Slack](https://nginxcommunity.slack.com/)!
17+
## F5 Support
1618

17-
If you are not a member, click [here](https://community.nginx.org/joinslack) to sign up (and let us know if the link does not seem to be working!)
19+
If you’re an F5 customer with NGINX Plus and an active support contract, please contact [F5 Technical Support](https://www.f5.com/services/support).
1820

19-
Once you join, check out the `#beginner-questions` and `nginx-users` channels :)
21+
<br/>
2022

21-
### Documentation
23+
## Documentation
2224

23-
For a comprehensive list of all NGINX directives, check out <https://nginx.org>.
25+
For a comprehensive list of all NGINX directives, check out <http://nginx.org/en/docs/dirindex.html>.
26+
27+
For a comprehensive list of all NGINX variables, check out <http://nginx.org/en/docs/varindex.html>.
28+
29+
For a comprehensive list of admin and deployment guides for NGINX Plus, check out <https://docs.nginx.com/nginx/admin-guide/>.
2430

2531
For a comprehensive list of admin and deployment guides for all NGINX products, check out <https://docs.nginx.com>.
2632

33+
</br>
34+
2735
### Mailing List
2836

2937
Want to get in touch with the NGINX development team directly? Try using the relevant mailing list found at <https://mailman.nginx.org/mailman3/lists/>!
3038

39+
<br/>
40+
3141
## Contributing
3242

3343
Please see the [contributing guide](https://github.com/nginxinc/nginx-azure-workshops/blob/main/CONTRIBUTING.md) for guidelines on how to best contribute to this project.
3444

45+
<br/>
46+
3547
## Commercial Support
3648

3749
Commercial support for this project may be available. Please get in touch with [NGINX sales](https://www.nginx.com/contact-sales/) or check your contract details for more info!
50+
51+
<br/>
52+
53+
### Community Slack
54+
55+
We have a community [Slack](https://nginxcommunity.slack.com/)!
56+
57+
If you are not a member, click [here](https://community.nginx.org/joinslack) to sign up (and let us know if the link does not seem to be working!)
58+
59+
Once you join, check out the `#beginner-questions` and `nginx-users` channels :)

0 commit comments

Comments
 (0)