Skip to content

fix(chart): default agent and operator images to ghcr.io - #2591

Open
Rémi BUISSON (darkweaver87) wants to merge 2 commits into
microsoft:mainfrom
darkweaver87:fix/default-agent-operator-images-to-ghcr
Open

fix(chart): default agent and operator images to ghcr.io#2591
Rémi BUISSON (darkweaver87) wants to merge 2 commits into
microsoft:mainfrom
darkweaver87:fix/default-agent-operator-images-to-ghcr

Conversation

@darkweaver87

@darkweaver87 Rémi BUISSON (darkweaver87) commented Jul 28, 2026

Copy link
Copy Markdown

Motivation

The retina-hubble chart defaults the agent and operator images to acndev.azurecr.io, an internal registry that isn't reachable outside Microsoft, so a stock helm install of the published chart lands in ImagePullBackOff. The retina-init image, and the standard chart's agent/operator, already default to ghcr.io/microsoft/retina/*; this aligns the hubble chart with them. Only the two default repositories change — rendered output is otherwise identical.

Signed-off-by: darkweaver87 <remi-buisson@orange.fr>
repository: acndev.azurecr.io/retina-operator
repository: ghcr.io/microsoft/retina/retina-operator
pullPolicy: Always
tag: "latest"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we've ever published latest tags for any images, we should pin this to a released version tag

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch — done. The three Retina image tags now default to .Chart.Version (the released chart version, e.g. v1.2.3) when left empty, instead of latest; --set <image>.tag=… still overrides. Verified with helm package --version + helm template — which is exactly what release-charts.yaml (L55-56) does, so the published chart's .Chart.Version is the release tag.

… latest

Signed-off-by: darkweaver87 <remi-buisson@orange.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants