Currently the chart release include only the AppConfig controller, but not OAM workload/traits.
If users want to deploy OAM apps, they need to do additional cumbersome steps:
git clone [email protected]:crossplane/addon-oam-kubernetes-local.git
kubectl create namespace oam-system
helm install controller -n oam-system ./charts/oam-core-resources/
As discussed previously, we want to have the workload/trait controllers in the chart release too. This issue is created to discuss details and track progress.
cc @negz @hasheddan @ryanzhang-oss @resouer @wonderflow @artursouza
Yes, similar discussion was brought up in slack channel.
Today, we have multiple entries to install Crossplane with OAM core controllers (addon-local/remote), it's painful to re-direct users across different orgs/repos.
We have:
helm install, very simpleIdeally, it would be great to include addon-local/remote in Crossplane helm charts so the installation will be as simple as:
helm install --name crossplane --namespace crossplane-system crossplane-alpha/crossplane --set addon=local
I'm working on this, my plan is:
addon-oam-kubernetes-local and addon-oam-kubernetes-remote configurable by using helm values, addon-oam-kubernetes-local as default.What about your ideas?
@negz @hongchaodeng @resouer @ryanzhang-oss
Per https://github.com/crossplane/oam-kubernetes-runtime/issues/55 we're planning to modularise this, so OAM controllers will be installable without the core Crossplane controllers and vice versa as distinct Helm charts.
Most helpful comment
Yes, similar discussion was brought up in slack channel.
Today, we have multiple entries to install Crossplane with OAM core controllers (addon-local/remote), it's painful to re-direct users across different orgs/repos.
We have:
helm install, very simpleIdeally, it would be great to include addon-local/remote in Crossplane helm charts so the installation will be as simple as: