deploy should not need go environment

[JingChen23]

Signed-off-by: Chen Jing jingch@vmware.com

Description

This change contains 2 improvements.

1. Change the imagePullPolicy to IfNotPresent to save unnecessary download.
2. when user run ./deploy.sh install, they will call below functions in Makefile:
   deploy -> manifests -> controller-gen -> tidy
   But I don't think running tidy during deployment is the right behaviour.

We can let the developer run go tidy at debug or build stage, but never at deployment stage. This doesn't make sense.

This makes the user must install go 1.19 in the machine, this doesn't make sense neither

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (main@4746bcb). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage        ?   45.57%           
=======================================
  Files           ?        6           
  Lines           ?      814           
  Branches        ?        0           
=======================================
  Hits            ?      371           
  Misses          ?      414           
  Partials        ?       29           

Flag	Coverage Δ
unittests	45.57% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[4everming]

Thanks for raising out this improvement. That's indeed what we'd like to do.
Please check this dependency in Makefile: deploy -> kustomize -> go-get-tool function.
It seems like it cannot eliminate the go sdk dependency with the code in this PR if that is what you'd like to do. I suggest adding a new user-facing target in Makefile to make CNSI can be deployed without go sdk.