Skip to content

Include all Prow cluster dependencies in renovate config #1440

Description

@lentzi90

Expand the renovate.json to include:

Those above should be straight forward.
Then we have a few that will require more. We can add these to renovate also for notification, but they will in general require some manual actions and/or additional automation than just bumping the version.

  • Kubernetes versions in https://github.com/metal3-io/project-infra/tree/main/prow/capo-cluster
    This requires making sure there are new disk images available. Templates cannot be updated, we need to create new templates and roll over to them.
  • CPO version:
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/controller-manager/cloud-controller-manager-roles.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/controller-manager/cloud-controller-manager-role-bindings.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/controller-manager/openstack-cloud-controller-manager-ds.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/cinder-csi-plugin/cinder-csi-controllerplugin-rbac.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/cinder-csi-plugin/cinder-csi-controllerplugin.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/cinder-csi-plugin/cinder-csi-nodeplugin-rbac.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/cinder-csi-plugin/cinder-csi-nodeplugin.yaml
    - https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/v1.35.0/manifests/cinder-csi-plugin/csi-cinder-driver.yaml

    These are straight forward to apply, but should be kept in sync with the Kubernetes version. In that sense this is usually done together with the Kubernetes upgrades.
  • Autoscaler version:
    Same as above. Straight forward but should be done in sync with Kubernetes.
  • Gateway API:
    - https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.5.1/standard-install.yaml

    Nothing special except that we must ensure the Traefik version is compatible. Should usually be done together with Traefik.
  • Traefik version: and
    # helm template traefik traefik/traefik --version 41.0.0 \
    and
    - https://github.com/traefik/traefik-helm-chart/traefik/crds?ref=v41.0.0

    Here we have to juggle multiple things. There is the helm chart version, the Traefik version and the CRDs (which follow the helm chart version). We generate the resources.yaml from the helm chart (see comment at the top of that file).

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/ciCategorizes issue or PR as related to CI or testing.triage/acceptedIndicates an issue is ready to be actively worked on.

    Type

    Projects

    Status
    MISC WIP

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions