Add FAQ from kubectl.docs.kubernetes.io

[ashnehete]

Add the following to docs:

1. FAQ
2. Eschewed Features at /contribute/features/eschewedfeatures/
3. Versioning Policy at /docs/reference/versioningpolicy/

Links to glossary items are broken because the page isn't populated yet.

Part of #4338

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ashnehete
Once this PR has been reviewed and has the lgtm label, please assign ncapps for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• site/OWNERS

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

[k8s-ci-robot]

Welcome @ashnehete!

It looks like this is your first PR to kubernetes-sigs/kustomize 🎉. 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-sigs/kustomize 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 @ashnehete. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

[ashnehete]

/ok-to-test

[k8s-ci-robot]

@ashnehete: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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-sigs/prow repository.

[k8s-ci-robot]

This PR has multiple commits, and the default merge method is: merge.
You can request commits to be squashed using the label: tide/merge-method-squash

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-sigs/prow repository.

[ashnehete]

Also adds the following:

1. Set sidebar_menu_compact=true. This improves readability of the big sidebar menu. Also how it is currently on kubectl.docs.kubernetes.io.
2. Add Kustomize Enhancement Proposal title to Contributing Features to improve clarity.

[ashnehete]

Also adds the following:

1. Glossary
2. Fix broken links

[ChristianCiach]

About the Removal directives: Kustomize offers the $delete operation for strategic merge patches and they are officially supported: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md#basic-patch-format

I feel like stating that Kustomize does not offer "removal directives" seems a bit misleading.

[stormqueen1990]

Hi there, @ashnehete!

Thank you very much for your contribution! I found some small textual issues that I believe were already in the original doc, but would be nice to fix before we merge this one. Other than that, this looks good to me!

[eddiezane]

/ok-to-test