* Used images tag to inject image override to clustetctl object,
the same way the image override is done for cert-manager.
* Using this way, the upstream manifests for cluster components does
not need any customization (IMAGE URL as variable) and can be consumed as is.
* If this approach is approved, then will update the same for other proviers
( CAPO, CAPD, CAPZ, cAPG ) and will get tested.
Change-Id: If920f544d111d94e5b7075d5406ed2f87a5e6929
Closes: #431
This reverts commit 813bdd3614d13cc6bacbf0846c139d8f6da027af.
Reason for revert: This commit was done to avoid duplication of certmanager across all clusterctl components. However with the current notion of maintaining the upstream version as is, this change should be reverted. Also there is WIP to implement cert-manager as a standalone component even before clusterctl tries to deploy its embedded certmanager. So this commit will avoid manipulating the override in the standalone certmanager component
Change-Id: I16b0b002da990eb3f070f69d025cb904f7ef9e27
* Remove the duplicated certmanager across all the
cluster components ( capi, capm3, cacpk, cbk, capd, capz)
and use certmanager from functions ( global )
Change-Id: I9ee060a19ab8c9eb508bc3ddb848895478170b98
Closes: #350
This allows for container locations and versions for the CAPI functions
to be (optionally) driven by the `versions-airshipctl` versions
catalogue. In addition, this moves the clusterctl config from the site
level to become its own function, which can be further refined
(e.g. for public cloud providers) via inheriting functions, composites,
types, etc.
Change-Id: Ic2b02e256419ee8536f5237327cce2754fd0abff
Closes: https://github.com/airshipit/airshipctl/issues/316
