Deploy operator with single YAML manifest

[spilchen]

Now that our operator is cluster scoped, we can deploy it using simple kubectl apply -f ... commands. This adds that manifest to our release artifacts. This will be published on GitHub in our 2.0.0 release. Once released the command will be:

# Install CRDs
kubectl apply --server-side=true --force-conflicts -f https://github.com/vertica/vertica-kubernetes/releases/latest/download/verticadbs.vertica.com-crd.yaml
kubectl apply --server-side=true --force-conflicts -f https://github.com/vertica/vertica-kubernetes/releases/latest/download/verticaautoscalers.vertica.com-crd.yaml
kubectl apply --server-side=true --force-conflicts -f https://github.com/vertica/vertica-kubernetes/releases/latest/download/eventtriggers.vertica.com-crd.yaml
# Deploy the operator
kubectl apply -f https://github.com/vertica/vertica-kubernetes/releases/latest/download/operator.yaml

[roypaulin]

I get the idea but what about all the parameters that are usually set on helm charts?

[spilchen]

I get the idea but what about all the parameters that are usually set on helm charts?

The manifest just has the default values for those. That is good enough to deploy the operator. If you need a customized deployment, helm is still the way to go.