-
Notifications
You must be signed in to change notification settings - Fork 48
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
Update Makefile
for simplified local development using Skaffold
#599
Update Makefile
for simplified local development using Skaffold
#599
Conversation
Closing this PR as |
Reopening the pull request. The |
If it's only for local development, can we also find a way to provide desired flags to controller container? We should be able to annotate as well based on Developer's wish |
That needs to be manually changed from the Helm template here if necessary. Subsequently, if we execute make deploy, the corresponding changes will be applied. |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@seshachalam-yv thanks for the PR. Overall LGTM.
- Can you please add this line to
Makefile
targetmake kind-up
to make it easy for developers to set theKUBECONFIG
of the new KinD cluster before they runmake deploy
?
@echo -e "Please run the following command to target the newly created KinD cluster: \n export KUBECONFIG=hack/e2e-test/infrastructure/kind/kubeconfig"
Can you also please add a release note, since this is a breaking change for developers who are actively using make deploy
who will now need to move to `make deploy-via-kustomize? Thanks.
Makefile
Outdated
deploy: manifests $(KUSTOMIZE) | ||
kubectl apply -f config/crd/bases | ||
kustomize build config/default | kubectl apply -f - |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please provide a new Makefile
target make deploy-via-kustomize
? Since the repo still supports kustomize-based deployments, and there might be developers who might actually prefer this method, we should not completely remove it, and atleast provide a Makefile target for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, Shreyas, for nice suggestion.
Fixed as part of 231818f.
…mize` to support kustomize-based deployments.
This commit enhances the `make kind-up` command by adding a console message that instructs the user to set the KUBECONFIG environment variable for the newly created KinD cluster. ``` bash 📌 NOTE: To target the newly created KinD cluster, please run the following command: export KUBECONFIG=/Users/I568019/work/etcd-druid/hack/e2e-test/infrastructure/kind/kubeconfig ```
Fixed as part of a6cf748
Updated release note. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@seshachalam-yv thanks for addressing my comments.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
How to categorize this PR?
/area dev-productivity
/kind enhancement
What this PR does / why we need it:
This PR updates the
Makefile
to useSkaffold
for deploying theetcd-druid
. It replaces the use ofkustomize
withSkaffold
and it builds the image from the current code base and deploys the pod. This approach simplifies the deployment process and eliminates the need to push the image to the container registry for each local development testing.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: