Skip to content
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

Migrate access control example to documentation website #6572

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

ADubhlaoich
Copy link
Contributor

@ADubhlaoich ADubhlaoich commented Oct 2, 2024

Proposed changes

This pull request migrates the access control example to the documentation website, converting the existing README into a page formatted for the production website. It also cleans up the frontmatter of the surrounding documents so that pages can be more easily re-arranged in the future.

The converted page makes use of single source embedded code blocks using files in the GitHub repository, as well as a highlighting feature of code blocks that has not been used in previous documentation.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

This commit migrates the access control example to the documentation
website, converting the existing README into a page formatted for the
production website. It also cleans up the frontmatter of the surrounding
documents so that pages can be more easily re-arranged in the future.

The converted page make use of single source embedded code blocks using
files in the GitHub repository, as well as a highlighting feature of
code blocks that has not been used in previous documentation.
@ADubhlaoich ADubhlaoich requested review from a team as code owners October 2, 2024 11:17
@ADubhlaoich ADubhlaoich self-assigned this Oct 2, 2024
@github-actions github-actions bot added the documentation Pull requests/issues for documentation label Oct 2, 2024
@ADubhlaoich ADubhlaoich added the needs cherry pick Cherry pick this PR into a release branch label Oct 2, 2024
Copy link

github-actions bot commented Oct 2, 2024

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/nginx-ingress-controller/6572/

@@ -1,96 +1,3 @@
# Access Control
# Deploy an Access Control policy
Copy link
Contributor

@vepatel vepatel Oct 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Access Control is a feature and policy is one of the steps so the original title is apt

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original title does not describe the intent of the document, and the new one is matched to the website document, which is written as an instruction.

Copy link

codecov bot commented Oct 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.00%. Comparing base (e750d84) to head (91387ef).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6572      +/-   ##
==========================================
- Coverage   53.08%   53.00%   -0.08%     
==========================================
  Files          87       87              
  Lines       16200    16223      +23     
==========================================
  Hits         8599     8599              
- Misses       7194     7217      +23     
  Partials      407      407              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

IC_IP=<ip-address>
```

2. The HTTP port of the same instance
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. The HTTP port of the same instance
2. The HTTP port of the same instance.


{{< ghcode "https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/refs/heads/main/examples/custom-resources/access-control/webapp.yaml" >}}

Apply it using *kubectl*:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should 'kubectl' be formatted as code instead?


## Configure load balancing

Create a file named *virtual-server.yaml* for the VirtualServer resource. The *policies* field references the example application.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Create a file named *virtual-server.yaml* for the VirtualServer resource. The *policies* field references the example application.
Create a file named *virtual-server.yaml* for the VirtualServer resource. The *policies* field references the access control Policy created in the previous section.


---

## Deploy an Access Control policy
Copy link
Contributor

@jputrino jputrino Oct 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Deploy an Access Control policy
## Deploy a Policy to deny access to your app


---

## Update the policy
Copy link
Contributor

@jputrino jputrino Oct 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Update the policy
## Deploy a Policy to allow access to your app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Pull requests/issues for documentation needs cherry pick Cherry pick this PR into a release branch
Projects
Status: Todo ☑
Development

Successfully merging this pull request may close these issues.

3 participants