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
With each release, we should generate the static manifests from the helm and place them under deploy/manifests.
Perhaps we need to extend the functionality of the existing workflow
The text was updated successfully, but these errors were encountered:
Hi @davidkornel, if I get this right, this would be very helpful, as I'd be able to use the manifests through Kustomize (kubectl apply -k) without Helm. Not sure if the static manifests are up-to-date right now.
hi @davidknezic, my bad I forgot to update them with the latest release, they are still at v0.15.0. I'll try to update them tonight. Feel free to send a ping if I forget to update.
@davidknezic they should be up-to-date know. As it was stated in the commit message by default the legacy dataplane mode is used, however a sample Dataplane CR is also provided. If you wish to use the dataplane mode:
change the dataplane-mode flag to managed in the stunner-gateway-operator-manifests.yaml file
With each release, we should generate the static manifests from the helm and place them under deploy/manifests.
Perhaps we need to extend the functionality of the existing workflow
The text was updated successfully, but these errors were encountered: