You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Besides the issues in the control plane container (with fixes being merged in #313, there are also minor issues in the current Kustomize files:
Outdated kube-rbac-proxy image in the control plane
The control plane uses the outdated gcr.io/kubebuilder/kube-rbac-proxy:v0.13.0 image (reference).
Considering that the control plane is now actively being developed in Rust, this proxy might no longer be necessary. These manifests looks like the leftovers from kubebuilder scaffolding.
Incorrect binary name in default manifests
The default manifests in config/ point to an incorrect binary name
Besides the issues in the control plane container (with fixes being merged in #313, there are also minor issues in the current Kustomize files:
Outdated
kube-rbac-proxy
image in the control planegcr.io/kubebuilder/kube-rbac-proxy:v0.13.0
image (reference).Incorrect binary name in default manifests
config/
point to an incorrect binary nameblixt/config/manager/manager.yaml
Line 38 in 0858e92
/workspace/manager
, (as per fix: update Containerfile.controlplane to include the correct binary and run as non-root #313).Incorrect ports in the data plane configuration
blixt/config/dataplane/dataplane.yaml
Lines 39 to 49 in 0858e92
9875
instead of9874
.The text was updated successfully, but these errors were encountered: