feat(*): Bumps to 0.2 for wasmcloud 1.0 support

This bumps both the version of the operator and the default host version
in the example to 1.0. Also updates the README to use the released wadm
chart

Signed-off-by: Taylor Thomas <taylor@cosmonic.com>
This commit is contained in:
Taylor Thomas 2024-04-17 16:47:23 -06:00
parent 692d78308b
commit a947d144cb
5 changed files with 10 additions and 12 deletions

2
Cargo.lock generated
View File

@ -4415,7 +4415,7 @@ dependencies = [
[[package]]
name = "wasmcloud-operator"
version = "0.2.0-alpha.1"
version = "0.2.0"
dependencies = [
"anyhow",
"async-nats",

View File

@ -1,6 +1,6 @@
[package]
name = "wasmcloud-operator"
version = "0.2.0-alpha.1"
version = "0.2.0"
edition = "2021"
[[bin]]

View File

@ -105,13 +105,8 @@ helm upgrade --install -f values.yaml nats-cluster nats/nats
### Running Wadm
You can deploy Wadm to your Kubernetes cluster with the Wadm Helm chart. First, clone the Wadm repo from GitHub:
```shell
git clone https://github.com/wasmCloud/wadm.git
```
In the cloned repo, find the chart at `wadm/charts/wadm`. For a minimal deployment, all you need in your `values.yaml` file is:
You can run Wadm in your Kubernetes cluster using our Helm chart. For a minimal deployment using the
NATS server deployed above, all you need in your `values.yaml` file is:
```yaml
wadm:
@ -119,8 +114,11 @@ wadm:
nats:
server: "nats-cluster.default.svc.cluster.local:4222"
```
You can deploy Wadm using your values file and Helm:
```sh
helm install wadm -f values.yaml ./
helm install wadm -f values.yaml --version 0.2.0 oci://ghcr.io/wasmcloud/charts/wadm
```
### Start the operator

View File

@ -15,7 +15,7 @@ spec:
spec:
serviceAccountName: wasmcloud-operator
containers:
- image: ghcr.io/wasmcloud/wasmcloud-operator:latest
- image: ghcr.io/wasmcloud/wasmcloud-operator:0.2.0
imagePullPolicy: Always
name: wasmcloud-operator
ports:

View File

@ -13,7 +13,7 @@ spec:
hostLabels:
test: value
# Which wasmCloud version to use
version: 1.0.0-rc.2
version: "1.0.0"
# The name of a secret in the same namespace that provides the required secrets.
secretName: cluster-secrets
logLevel: INFO