Skip to content
This repository was archived by the owner on Feb 15, 2025. It is now read-only.

chore: use upstream containers in upstream flavored packages #1138

Open
justinthelaw opened this issue Sep 25, 2024 · 0 comments
Open

chore: use upstream containers in upstream flavored packages #1138

justinthelaw opened this issue Sep 25, 2024 · 0 comments
Labels
chore dependencies Pull requests that update a dependency file tech-debt Not a feature, but still necessary
Milestone
Next (M11) - Conf...

Comments

@justinthelaw
Copy link
Contributor

justinthelaw commented Sep 25, 2024 •
edited
Loading

Describe what should be investigated or refactored

We currently use a Chainguard bash (latest) image and a self-packaged Python image as our package / job base images. The upstream flavor should come from upstream, non-bespoke/pay-walled, container registries. Change all instances where images are using improper upstream sources.

Links to any relevant code

See all packages, deployment/values manifests and Dockerfiles.

Additional context

N/A
@justinthelaw justinthelaw added dependencies Pull requests that update a dependency file tech-debt Not a feature, but still necessary chore labels Sep 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
chore dependencies Pull requests that update a dependency file tech-debt Not a feature, but still necessary
Projects
None yet
Milestone
Next (M11) - Conformance | Stability ...
Development

No branches or pull requests
1 participant
@justinthelaw