Getting latest changes to main-dev branch

.gitignore

@@ -26,3 +26,6 @@
 
 # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
 hs_err_pid*
+
+# generated docs
+en/site

README.md

@@ -1,2 +1,129 @@
-# docs-apk
-Documentation for WSO2 APK, which is an API platform for Kubernetes.
+# Documentation for WSO2 API Platform for Kubernetes
+
+## Prerequisites
+### Ubuntu
+
+#### Add the required repositories and updating:
+The first step is to add the required repositories and update the system. The command `sudo add-apt-repository ppa:deadsnakes/ppa` adds the PPA (Personal Package Archive) maintained by the Python packages team, and the `sudo apt-get update` command updates the packages list on the Ubuntu system.
+
+
+#### Install Python 3.10:
+The next step is to install Python 3.10 on Ubuntu.
+```bash
+sudo apt install python3.10 python3.10-distutils
+```
+Verify the installation by checking the version of Python 3.10:
+
+If installation is successful, `python3.10 --version` should give the output `Python 3.10.10`
+
+
+#### Install pip:
+After installing Python, the next step is to install Pip, the package installer for Python. 
+```bash
+curl -sS https://bootstrap.pypa.io/get-pip.py | python3.10
+```
+If you get a warning to update the path, it is required to do so. You can add the following line to your shell configuration file (e.g., .bashrc, .zshrc) to update the PATH environment variable:
+```bash
+export PATH="$PATH:/home/<your-user-name>/.local/bin"
+```
+
+This ensures that the Pip binaries are added to the PATH so that you can use Pip to install packages without specifying the full path to the binary.
+
+```bash
+pip3.10 --version
+````
+
+It should give the output `pip 23.0.1 from <path-to-pip> (python 3.10)`.
+
+
+### macOS
+
+#### Installing Python 3.10
+1. Download the latest version of Python 3.10 from the official website (https://www.python.org/downloads/macos/).
+
+2. Double-click the downloaded package to start the installation process.
+
+3. Follow the on-screen instructions to complete the installation. Make sure to select "Install for all users" and "Add Python 3.10 to PATH" options.
+
+4. After the installation is complete, open the Terminal app.
+
+5. Type `python3.10 --version` or `python3.10 -V` in the Terminal and press Enter. If Python 3.10 is installed correctly, you should see the version number printed in the Terminal.
+
+#### Installing pip
+Open the Terminal app.
+
+Copy and paste the following command into the Terminal and press Enter:
+
+```bash
+curl -sS https://bootstrap.pypa.io/get-pip.py | python3.10
+```
+This command will download and install the latest version of pip for Python 3.10.
+
+After the installation is complete, type `pip3.10 --version` or `pip3.10 -V` in the Terminal and press Enter. If pip is installed correctly, you should see the version number printed in the Terminal.
+
+## Installing and Running mkdocs
+Once you complete the prerequisite the following steps are common to both macOS and Ubuntu.
+
+First change directory to the `en` folder.
+
+#### Install MkDocs:
+The next step is to install MkDocs, a static site generator that is used to create documentation sites.
+```bash
+pip3.10 install mkdocs==1.4.2
+```
+#### Install the MkDocs plugins:
+In order to use some of the advanced features of MkDocs, you need to install some plugins. The following commands install the required plugins:
+
+Method 1. Using requirements.txt
+
+```bash
+pip3.10 install -r requirements.txt
+```
+
+Method 2. Individually.
+
+```bash
+pip3.10 install mkdocs==1.4.2
+pip3.10 install Pygments==2.14.0
+pip3.10 install mkdocs-material==9.1.2
+pip3.10 install pymdown-extensions==9.10
+pip3.10 install mkdocs-minify-plugin==0.6.2
+pip3.10 install mkdocs-markdownextradata-plugin==0.2.5
+pip3.10 install mkdocs-redirects==1.2.0
+pip3.10 install pathlib==1.0.1
+pip3.10 install markdown-include==0.8.1
+pip3.10 install markdown==3.2.1
+pip3.10 install mkdocs-exclude==1.0.2
+pip3.10 install jinja2==3.1.2
+```
+
+These plugins provide support for syntax highlighting, a Material Design theme, extended Markdown syntax, and various other features.
+
+#### Running MkDocs
+Once you have installed MkDocs and the required plugins, you can start a local development server by running the following command. 
+```bash
+python3.10 -m mkdocs serve
+```
+This command serves the documentation site locally, allowing you to preview changes as you make them.
+
+#### Build for Production
+To build the site for production, run the following command.
+
+```bash
+python3.10 -m mkdocs build
+```
+
+This generates the static site files in the site directory, which can be deployed to a web server.
+
+### Trouble shooting
+##### Error while installing minify plugin.
+Solution: Run the following and retry.
+
+```bash
+pip3.10 install --upgrade setuptools
+```
+
+##### Tabs are not rendering properly.
+Follow the new syntax. https://squidfunk.github.io/mkdocs-material/reference/content-tabs/?h=tabs#usage
+
+When the tabs are supposed to render as child elements of a numbered list, fixing the indentation will fix most of the issues. The default space for indentation is 4 spaces.

en/docs/about-apk/FAQs.md

@@ -0,0 +1,226 @@
+# Frequently Asked Questions (FAQs)
+
+## About WSO2 APK
+### 1. What is WSO2 APK?
+
+WSO2 API Platform for Kubernetes (APK) is WSO2's cloud native API management platform to help you build, deploy, and manage APIs in a cloud environment. It is designed to be highly available and able to handle large numbers of API requests without performance degradation, with features like rate limiting, automatic failover and load balancing. For more information, refer the [What is APK?](./what-is-apk.md) section. 
+
+### 2. What is the open source license of the APK?
+
+[Apache Software License Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
+
+### 3. What are the technologies used in WSO2 APK?
+
+APK natively uses several Kubernetes features. Envoy is used for the API gateway implementation and Helm is used as a package manager. For more details, refer to the [Technologies Used](./architecture.md#technologies-used) section.
+
+### 4. What are the advantages of APK over APIM?
+
+APK is primarily meant for anyone who wants API management in the Kubernetes domain. Since APK leverages native Kubernetes features, it can easily scale and perform optimally in a Kubernetes environment. The WSO2 APK also has a microservice architecture, which enables higher flexibility and scalability across all of its components.
+
+## Installation and Deployment
+
+### 1. What are the minimum requirements needed to run WSO2 APK?
+
+Refer to the [prerequisites](../setup/prerequisites.md) section for this information.
+
+### 2. I want to customize some configurations in my Helm deployment. How can I do this?
+
+Refer to the [customize configurations](../setup/Customize-Configurations.md) section for this information.
+
+### 3. What are the Kubernetes distributions supported by WSO2 APK?
+
+Minikube, Rancher, Kind and Openshift are supported. For more information about the supported versions, please refer to the [supported Kubernetes distributions](../setup/prerequisites.md#kubernetes-distributions) section.
+
+### 4. Why are pods not transitioning to the running state for a long time?
+
+If pods are taking an extended amount of time to transition to the running state, it is likely due to slow image pulling. This can occur when there are network connectivity issues, or if the image repository is experiencing a high load.
+
+You can troubleshoot the problem by running the following command
+```
+kubectl describe pods <pod-name>
+```
+
+If you see `ImagePullBackOff` error or the image is still in the pulling stage, it is most likely due to a network problem. 
+
+### 5. How can I uninstall APK from my cluster?
+
+1.  List down the Helm installation in your cluster using the following command, and copy the APK release name and the namespace.
+    ``` 
+    helm list -A
+    ```
+
+2.  Uninstall the APK 
+
+    === "Sample command"
+
+        ```
+        helm uninstall apk
+        ```
+
+    === "Command template"
+
+        ```
+        helm uninstall <apk-name> -n <namespace>
+        ```
+
+3.  Cleanup the CRs that were created for the APK. You can use the commands given below to delete all the CRs created for APK.
+
+    ```
+    kubectl delete apipolicies.dp.wso2.com --all --all-namespaces
+    kubectl delete apis.dp.wso2.com --all --all-namespaces
+    kubectl delete authentications.dp.wso2.com --all --all-namespaces
+    kubectl delete backendjwts.dp.wso2.com --all --all-namespaces
+    kubectl delete backends.dp.wso2.com --all --all-namespaces
+    kubectl delete certificaterequests.cert-manager.io --all --all-namespaces
+    kubectl delete certificates.cert-manager.io --all --all-namespaces
+    kubectl delete challenges.acme.cert-manager.io --all --all-namespaces
+    kubectl delete clusterissuers.cert-manager.io --all --all-namespaces
+    kubectl delete gatewayclasses.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete gateways.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete grpcroutes.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete httproutes.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete interceptorservices.dp.wso2.com --all --all-namespaces
+    kubectl delete issuers.cert-manager.io --all --all-namespaces
+    kubectl delete orders.acme.cert-manager.io --all --all-namespaces
+    kubectl delete ratelimitpolicies.dp.wso2.com --all --all-namespaces
+    kubectl delete referencegrants.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete scopes.dp.wso2.com --all --all-namespaces
+    kubectl delete tcproutes.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete tlsroutes.gateway.networking.k8s.io --all --all-namespaces
+    kubectl delete tokenissuers.dp.wso2.com --all --all-namespaces
+    kubectl delete udproutes.gateway.networking.k8s.io --all --all-namespaces
+    ```
+
+4. Delete all the APK related CRDs.
+   ```
+   curl -L -o apk.tar.gz "https://github.com/wso2/apk/archive/refs/tags/1.0.0.tar.gz" && tar -zxvf apk.tar.gz
+   cd apk-1.0.0/helm-charts/crds
+   kubectl delete -f .
+   ```
+
+5. Verify that you do not have any CRs in the cluster using this command.
+   ```
+    kubectl get apipolicies.dp.wso2.com -A
+    kubectl get apis.dp.wso2.com -A
+    kubectl get authentications.dp.wso2.com -A
+    kubectl get backendjwts.dp.wso2.com -A
+    kubectl get backends.dp.wso2.com -A
+    kubectl get certificaterequests.cert-manager.io -A
+    kubectl get certificates.cert-manager.io -A
+    kubectl get challenges.acme.cert-manager.io -A
+    kubectl get clusterissuers.cert-manager.io -A
+    kubectl get gatewayclasses.gateway.networking.k8s.io -A
+    kubectl get gateways.gateway.networking.k8s.io -A
+    kubectl get grpcroutes.gateway.networking.k8s.io -A
+    kubectl get httproutes.gateway.networking.k8s.io -A
+    kubectl get interceptorservices.dp.wso2.com -A
+    kubectl get issuers.cert-manager.io -A
+    kubectl get orders.acme.cert-manager.io -A
+    kubectl get ratelimitpolicies.dp.wso2.com -A
+    kubectl get referencegrants.gateway.networking.k8s.io -A
+    kubectl get scopes.dp.wso2.com -A
+    kubectl get tcproutes.gateway.networking.k8s.io -A
+    kubectl get tlsroutes.gateway.networking.k8s.io -A
+    kubectl get tokenissuers.dp.wso2.com -A
+    kubectl get udproutes.gateway.networking.k8s.io -A
+   ```
+
+    You should not see any resources. If there are any undeleted resources, use the command given below to delete them.
+
+    ```
+    kubectl delete <kind> <name> -n <namespace>
+    ```
+
+### 6. Why is my installation failing with an "ensure CRDs are installed first" error?
+
+If you are seeing errors similar to the ones below:
+
+```plaintext
+ensure CRDs are installed first, resource mapping not found for name: "apk-wso2-apk-dcr-api" namespace: "default" from "": no matches for kind "API" in version "dp.wso2.com/v1alpha2"
+```
+
+It is likely due to a limitation in Helm when installing the Custom Resource Definitions (CRDs). To resolve this, follow the steps below.
+
+Step 1: Obtain the CRDs from the chart
+
+First, obtain the Custom Resource Definitions (CRDs) for the specific version of APK you want to install. Replace `<version>` with the actual version number of the APK you are installing.
+
+```bash
+helm show crds wso2apk/apk-helm --version 1.1.0 > apk-crds.yaml
+```
+
+Step 2: Apply the CRDs manually
+
+Next, apply the CRDs using the following command.
+
+```bash
+kubectl apply -f apk-crds.yaml
+```
+
+Step 3: Reinstall APK
+
+Finally, reinstall APK using the Helm installation command as provided in the relevant quick start guide.
+
+```bash
+helm install apk wso2apk/apk-helm --version 1.1.0
+```
+
+## Functionality
+
+### 1. What are the API types supported by WSO2 APK?
+Currently, WSO2 APK only supports REST APIs.
+
+### 2. Can I perform API request/response transformations?
+
+Yes, you can. Refer to the [Interceptors](../create-api/create-and-attach-api-policies/api-policies-overview.md) for information on how to configure this.
+
+### 3. What are the CRDs used in WSO2 APK?
+
+Refer to the [CRD catalog](../catalogs/kubernetes-crds.md) for details on the CRDs used in the APK, including examples and the configuration definitions.
+
+## Security
+
+### 1. What are the different methods available for API authentication?
+Currently, APK supports OAuth 2.0 and mutualSSL for API authentication.
+
+### 2. Can I use a custom authorization header?
+Yes, a custom authorization header can be used. Refer to the [Use custom bearer header name](..//develop-and-deploy-api/security/authentication/enable-api-security/oauth2.md) for instructions to configure this.
+
+## Troubleshooting
+
+### 1. Why am I encountering 'Unknown field' errors during the installation process?
+
+If you are seeing errors similar to the ones below:
+
+```plaintext
+W0907 12:33:54.079420 1181879 warnings.go:70 unknown field "spec.someName"
+...
+Error: INSTALLATION FAILED: 7 errors occurred:
+   * API.dp.wso2.com "apk-wso2-apk-oauth-api" is invalid: [spec.apiDisplayName: Required value, spec.context: Required value]
+   ...
+```
+
+It is likely due to a limitation in Helm when updating Custom Resource Definitions (CRDs). Helm does not automatically redeploy existing CRDs, which can lead to conflicts. Downloading the chart and applying the CRDs manually will resolve the issue. Here are the steps to follow to achieve this.
+
+1.  Download the chart to your local environment.
+
+    === "Command"
+
+        ```
+        curl -L -o apk.tar.gz "https://github.com/wso2/apk/archive/refs/tags/1.0.0.tar.gz" && tar -zxvf apk.tar.gz
+        ```
+
+2.  Go to the apk-1.0.0/helm-charts/crds folder and apply the CRDs manually.
+
+    === "Command"
+
+        ```
+        cd apk-1.0.0/helm-charts/crds
+        kubectl apply -f .
+        ```
+
+3. Now uninstall the previous faulty deployment and reinstall the APK using Helm.
+
+---
+
+These FAQs should guide you through resolving any issues or queries you face while using WSO2 APK. If you still encounter difficulties, please feel free to contact our support team for further assistance.