Fixed typo "permanen"

[ryanwilsonperkin]

What this PR does / why we need it:

Fixed the use of the name "permanen-redirect" instead of "permanent-redirect" in some annotations for this test

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Which issue/s this PR fixes

How Has This Been Tested?

It has not, I am new to this project and would be happy to test it if need be, but it does not seem to be something that would necessarily need it (unless changed annotations break part of the test system)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[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: login-issues@jira.linuxfoundation.org

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.

[k8s-ci-robot]

Welcome @ryanwilsonperkin!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. 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/ingress-nginx 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]

Hi @ryanwilsonperkin. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[aledbf]

/ok-to-test

[aledbf]

/check-cla

[aledbf]

@ryanwilsonperkin please sign the CLA

[codecov-commenter]

Codecov Report

Merging #5971 into master will increase coverage by 0.06%.
The diff coverage is 53.12%.

@@            Coverage Diff             @@
##           master    #5971      +/-   ##
==========================================
+ Coverage   58.65%   58.71%   +0.06%     
==========================================
  Files          88       88              
  Lines        6951     6966      +15     
==========================================
+ Hits         4077     4090      +13     
- Misses       2425     2427       +2     
  Partials      449      449              

Impacted Files	Coverage Δ
cmd/nginx/main.go	5.37% <0.00%> (ø)
internal/ingress/annotations/class/main.go	54.54% <ø> (ø)
internal/ingress/controller/controller.go	49.41% <0.00%> (-0.18%)	⬇️
internal/ingress/types.go	0.00% <ø> (ø)
internal/watch/file_watcher.go	84.61% <ø> (ø)
internal/ingress/controller/nginx.go	30.10% <50.00%> (+0.10%)	⬆️
internal/ingress/controller/store/store.go	58.57% <50.00%> (-0.20%)	⬇️
cmd/nginx/flags.go	82.56% <100.00%> (+0.18%)	⬆️
internal/ingress/annotations/proxyssl/main.go	95.65% <100.00%> (+0.33%)	⬆️
internal/ingress/controller/checker.go	39.13% <100.00%> (+3.41%)	⬆️
... and 2 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b31b9a...017a24f. Read the comment docs.

[ryanwilsonperkin]

@ryanwilsonperkin please sign the CLA

@aledbf all done now 👍

[aledbf]

/lgtm
/approve

[aledbf]

@ryanwilsonperkin thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, ryanwilsonperkin

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 [aledbf]

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