aws-quickstart
[Draft] Feature: KNative Operator addon
Issue #, if available: #490
Description of changes: Add support for the KNative operator v1.8 through a blueprint add-on. Included test ensures that the blueprint is defined after adding the KNative AddOn. Currently draft as it includes a copy of the operator yaml in the source, will update it with a remote download soon, also need to fix issues with Istio not deploying properly before KNative. Need to also add in the required lines of code to the BlueprintConstruct module for a showcase.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Latest update, Moved to remote YAML format that'll get update by KNative (the end user will still have to manually update versions).
- Done - Removed .DS_STORE @17a44a2
- YAML installation of the eventing, serving and functions CRDs have custom YAML that aren't parsed by the js-yaml library that is used with CDK-EKS. KNative recommends using the operator or the custom YAML installations for production grade workloads and since we can't use one, I'm using the other. It will definitely be easier to support as we would only need to install the Operator to get full functionality of KNative. While with Eventing, Serving, and Functions installed separately, you would need to maintain parity between the three versions while updating KNative.
- There is currently no Helm Chart. For explanations I would refer to this long running github issue: https://github.com/knative/docs/issues/311
- Sounds good!
- Will add them soon! Is there anything specific that needs to be in there?
- Will add them soon! Is there anything specific that needs to be in there?
./docs/addons/index.md ./docs/addons/knative.md ./mkdocs.yml (for navigation).
Updated docs, have tested Knative deployment with it's dependencies (istio) and it deploys and functions well.
