Hi all As of now, *API Operator*[1] requires a lot of configurations if someone needs to *try it out *(PoC/quick start/demo). This breaks the user experience and will lose the interest of the users towards the API Operator. Following are some of the noticed issues from the initial discussion[2].
1. DockerHub account configuration (Kaniko job uses this configuration
to push built runtime image of api microgateway).
- Users have to go through *multiple editing* in configuration file
- Users have to *encode* credentials with base64
2. Download multiple distributions.
- *API Operator* distribution[3]
- CLI tool: *apictl* distribution[4]
*Solution:*
Enable the *apictl* tool itself to install *API Operator* and configure
docker registry configurations and credentials.
*Proposed commands:*
apictl install operator
After executing the above command, it would prompt the user to enter the
following
1. Docker registry url (if the user is using a private docker registry,
has to provide the value. Otherwise just press "return")
2. Docker registry repository name
3. Docker username
4. Docker password
Once these things are provided, *apictl* will create a *kubernetes-secret*
to be used by the Kaniko job. Finally, everything is configured and the
operator is up and running.
[1] https://operatorhub.io/operator/api-operator
[2] Attached PDF
[3] https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.1
[4] https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.1
Thanks
Best Regards
*Renuka Fernando* | Software Engineer | WSO2 Inc.
(m) +9476 6678 752 | Email: [email protected]
<http://wso2.com/signature>
Improving the K8S API Operator First Hand Experience.pdf
Description: Adobe PDF document
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
