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

Dependency tracking/renovate #30

Open
mxmxchere opened this issue Mar 6, 2024 · 1 comment
Open

Dependency tracking/renovate #30

mxmxchere opened this issue Mar 6, 2024 · 1 comment
Assignees
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling

Comments

@mxmxchere
Copy link
Contributor

We need a dependency tracker, maybe renovate as we did in v1

@jschoone jschoone added the Container Issues or pull requests relevant for Team 2: Container Infra and Tooling label Mar 7, 2024
@DEiselt DEiselt self-assigned this Mar 12, 2024
@DEiselt
Copy link
Contributor

DEiselt commented Mar 12, 2024

I created a Fork for onboarding / testing purposes.

From what i understand so far, this will only apply to the helm dependencies defined in cluster-addon, as Docker / Kubernetes is defined through the directory structure deliberately.

I am also unsure if there are relations between the versions of deps in the cluster-addon to other versions and how this all relates to the structure ("providers/openstack/alpha/1-28"). If yes, we should consider pinning ranges in the helm dependencies Chart.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling
Projects
Status: Backlog
Development

No branches or pull requests

3 participants