-
Notifications
You must be signed in to change notification settings - Fork 532
Image Registry Inconsistencies #11502
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: suyog shinde <[email protected]>
Can anyone help me with this, The labeler is failing |
@@ -27,7 +27,7 @@ help: ## Output the self-documenting make targets | |||
ROOTDIR := $(shell pwd) | |||
OUTPUT_DIR ?= $(ROOTDIR)/_output | |||
|
|||
export IMAGE_REGISTRY ?= ghcr.io/kgateway-dev |
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.
we need to see if this works for publishing.
we have 2 repos - we push to ghcr.io/kgateway-dev
and pull from cr.gateway.dev
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.
Sure, How can we check that ?
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.
This is a good start, but we'll need additional changes to make sure it passes in CI. See 85ee04d for an attempt at this from a couple of weeks back.
/kind fix
fix: unify image registry configuration
Motivation:
There was an inconsistency in the image registry configuration across the Helm values, Makefile, and e2e manifests:
install/helm/kgateway/values.yaml
used:cr.kgateway.dev/kgateway-dev
ghcr.io/kgateway-dev
agent-gateway-integration.yaml
explicitly specified:ghcr.io/kgateway-dev
What Changed:
cr.kgateway.dev/kgateway-dev
as the defaultIMAGE_REGISTRY
, aligning with Helm.