Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify README/usage to address the current situation #177

Merged
merged 2 commits into from
Jan 26, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -331,11 +331,13 @@ build.cluster: $(KTF) # builds a KIND cluster which can be used for testing and
.PHONY: load.image
load.image: build.image
kind load docker-image $(BLIXT_CONTROLPLANE_IMAGE):$(TAG) --name $(KIND_CLUSTER) && \
kubectl -n blixt-system rollout restart deployment blixt-controlplane
kubectl -n blixt-system get deployment blixt-controlplane >/dev/null 2>&1 && \
kubectl -n blixt-system rollout restart deployment blixt-controlplane || true

.PHONY: load.all.images
load.all.images: build.all.images
kind load docker-image $(BLIXT_CONTROLPLANE_IMAGE):$(TAG) --name $(KIND_CLUSTER) && \
kind load docker-image $(BLIXT_DATAPLANE_IMAGE):$(TAG) --name $(KIND_CLUSTER) && \
kind load docker-image $(BLIXT_UDP_SERVER_IMAGE):$(TAG) --name $(KIND_CLUSTER) && \
kubectl -n blixt-system rollout restart deployment blixt-controlplane
kubectl -n blixt-system get deployment blixt-controlplane >/dev/null 2>&1 && \
kubectl -n blixt-system rollout restart deployment blixt-controlplane || true
19 changes: 17 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,13 +81,28 @@ to have _you_ join us in iterating on it and helping us build it together!
> (KIND)][kind] clusters. You can generate a new development cluster for
> testing with `make build.cluster`.

Deploy [Gateway API][gwapi] [CRDs][crds]:
> **Note**: Currently our container images are under migration from a private repository.
> At this moment, you should build and load images yourself.

1. Deploy [Gateway API][gwapi] [CRDs][crds]:

```console
kubectl apply -k https://github.com/kubernetes-sigs/gateway-api/config/crd/experimental?ref=v0.8.1
```

Deploy:
2. Build Blixt images:

```console
make build.all.images TAG=latest
```

3. Load images into your Kind cluster:

```console
make load.all.images TAG=latest
```

4. Deploy Blixt:

```console
kubectl apply -k config/default
Expand Down
Loading