Automatically updates properties of a Gardener CloudProfile, e.g. machineImages based on various sources, such as tags in an OCI repository.
- a recent
gocompiler - GNU
make dockerto build the container
The tests can be run with make check.
Initially, apply the ManagedCloudProfile CRD to your virtual garden apiserver.
Then a ManagedCloudProfile can be created:
apiVersion: cloudprofilesync.cobaltcore.dev/v1alpha1
kind: ManagedCloudProfile
metadata:
name: cloud-profile-name
spec:
cloudProfile:
# regular CloudProfile spec, but some fields are optional
# to enable fully automatic management
machineImageUpdates: # configures automatic management of machineImages
- imageName: gardenlinux
provider: # provider updates the providerConfig about images
ironcoreMetal: # updates gardener-extension-ironcore-metal
registry: docker.io # hostname of registry to pull the image from
repository: gardenlinux/gardenlinux # repository to pull the image from
source: # source used to check for image
oci: # OCI registry source
registry: docker.io # hostname of registry
repository: gardenlinux/gardenlinux # repository to watch
insecure: false # disables HTTP
username: "" # username for basic auth
password: "" # reference to a secret to lookup a password for basic auth
name: ""
namespace: ""
key: ""Reconciliation takes care of creating the respective CloudProfile.
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Copyright 2025 SAP SE or an SAP affiliate company and contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.