Skip to content
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

Enhance Makefile arguments for img building and pushing #47

Closed
ArangoGutierrez opened this issue Feb 22, 2022 · 6 comments · Fixed by #51
Closed

Enhance Makefile arguments for img building and pushing #47

ArangoGutierrez opened this issue Feb 22, 2022 · 6 comments · Fixed by #51
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ArangoGutierrez
Copy link
Contributor

Current Makefile doesn't provide flexible ways to modify how I want to build and push the image

VERSION := $(shell git describe --tags --dirty --always)
# Image URL to use all building/pushing image targets
IMAGE_BUILD_CMD ?= docker build
IMAGE_PUSH_CMD ?= docker push
IMAGE_BUILD_EXTRA_OPTS ?=
IMAGE_REGISTRY ?= k8s.gcr.io/kueue
IMAGE_NAME := controller
IMAGE_TAG_NAME ?= $(VERSION)
IMAGE_EXTRA_TAG_NAMES ?=
IMAGE_REPO ?= $(IMAGE_REGISTRY)/$(IMAGE_NAME)
IMAGE_TAG ?= $(IMAGE_REPO):$(IMAGE_TAG_NAME)
BASE_IMAGE_FULL ?= golang:1.17

Also in order to be more generic, rename
docker-image to simply image or image-build
docker-push to simply push or image-push

This provides more flexibility when developing in a non docker environment, like buildah , podman or even building the image with CI tool on kubernetes it self.

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 22, 2022
@ArangoGutierrez
Copy link
Contributor Author

Waiting for feedback
/assign

@ArangoGutierrez
Copy link
Contributor Author

@alculquicondor
Copy link
Contributor

Agree, not everyone uses docker :)

Do you really need the registry? The existing IMG parameter already allows you to use a full path.

@ArangoGutierrez
Copy link
Contributor Author

IMG is full path, splitting it down to registry + namespace + imagename + tag, is good when developing

@ArangoGutierrez
Copy link
Contributor Author

it works nice for use in NFD< bc we can set it to push to staging or other registries by simply editing an ENV VAR :) , but I am open to suggestion, once we agree here, I'll submit a patch

@alculquicondor
Copy link
Contributor

alculquicondor commented Feb 22, 2022

sounds good.

Since you have BASE_IMAGE_FULL, do you want to add one for the end image that is currently one of the distroless variants?

ChristianZaccaria pushed a commit to ChristianZaccaria/kueue that referenced this issue Jan 14, 2025
…mmadiIram-patch-1

Update renovate.json for tekton and dockerfile
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants