PR #35 introduced a small regression which only impacts clients who are
trying to use nonstandard ports. This fixes the problem by allowing the
NATS leaf node and client ports to be configured separately in the CRD.
Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
Add additional host options for the policy service, allowing insecure
registries and pulling the latest tag of an OCI ref.
Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
wasmCloud 1.0 fully converts over to using components among other large
changes, so we need to rework the operator to account for it. 1.0 is
still in the works, so this updates the operator to depend on wasmCloud
1.0 libraries along with refactoring the service creation code to use
the updated application manifest format.
Once this is in we will likely cut a 0.2.0 pre-release and wait for an
actual release until wasmCloud 1.0.0 and wadm 0.11 are out.
This also adds a new field to the CRD so that you can specify the full
image reference instead of just the version. The `image` parameter takes
precedence.
Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
This refactors the WasmCloudHostConfig CRD so that it has a single field
(`schedulingOptions`) for configuring how the underlying Pods are
scheduled in Kubernetes. This includes:
* Relocating the `daemonset` option to this new field
* Relocating the `resources` option to this new field
* Adding a new `pod_template_additions` field that allows you to set any
valid option in a `PodSpec`
Doing so allows cluster operators to do things like set node affinity
and node selector rules, along with any other valid PodSpec option. The
only thing that cannot be done is adding additional containers to the
pod, since that is all handled by the controller. We could look at
exposing that option if users want to be able to add additional
sidecars.
Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
Add documentation on how to use the `registryCredentialsSecret` to
enable wasmCloud hosts to pull from a private registry.
Also add comments to each of the CRD fields outlining what each field
does.
Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
Add a `daemonset` option for managing hosts as a DaemonSet instead of
just a Deployment.
Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
Dan Norris
Dan Norris