Some of sites defined in document model have no metadata.yaml,
which is essential to work properly with that sites.
* az-test-site and gcp-test-site metadata.yaml added
* metadata.yaml for test-site moved to appropriate directory
for consistency
Change-Id: Ibec109e41a5e3fd36794dc6a879888cfc610c9cc
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Relates-To: #19
Azure does not currently suport Calico networking.
As a workaround, this patch set includes CAPZ Calico manifests that uses
VXLAN, instead.
The CAPZ Calico manifest are located under
manifest/function/cni/calico-capz.
Change-Id: Iadb2d5e10131e6a2df8cef49e2ec189ab948eeb9
This patch set includes the site specifig for Azure (az-test-site) that
contains the manifests and kustomization files needed to deploy a
Workload cluster on the Azure cloud platform.
This patch set uses the Azure CAPZ v0.4.9 for the Workload cluster
deployment.
Change-Id: Ie71630bf55edadfcc11527c04aea41aa2161bdbd
This patch set includes the manifest templates for the Workload cluster
deployment for CAPZ v0.4.9.
Also, added the new folder manifest/function/workers-capz and moved the
manifests for v0.4.8 under it, as well as for v0.4.9
Change-Id: Ie08b6e7092f90ac8ee533c574a26eaf9b6600c5c
This patchset includes the manifests for CAPZ version v0.4.9, which has
been added under airshipctl/manifests/function/capz/v0.4.9
Also added an entry in the clusterctl/clusterctl.yaml for CAPZ
Change-Id: I3a52257320af1f68ec2d8f4302e7176b73f227dd
adjust openstack-test-site to execute the below phases
for openstack provider(capo)
clusterctl-init-ephemeral
controlplane-ephemeral
clusterctl-init-target
clusterctl-move
workers-target
A detailed test run of the phases can be found in
https://hackmd.io/OheCGmq8RX64SPw2sF3qGQ
Change-Id: Id982273d28515eb3a44c39d869eaeb229923339c
* Images added to clusterctl object like Providers
So that repository and tag for one or all of the cert-manager
components can be overriden using patch/replacement
clusterctl Documentation for Image Override:
https://cluster-api.sigs.k8s.io/clusterctl/configuration.html#image-overrides
Change-Id: Id9de8d1967e49aeb3293f6802e51d66d598333ae
Closes: #350
Update CAPO provider manifest to inherit clusterctl from
functions and patch the infrastructure provider details
Add capo versions in base-catalog
Change-Id: I8f1f59857dcbf163af01a5a766451e6579ded148
If a node has plenty (>16GB) of RAM, use a file-backed ext4 filesystem
for docker and ironic use. Otherwise, docker is unable to mount
container filesystems on top of the root overlayfs.
This is a fix on top of:
https://review.opendev.org/#/c/749096
Change-Id: Ib688edc6189a0b46e4a668c27cb6a11aca9bb0df
Closes: #401
* Change templater image tag from dev to latest
* Change replacement-transformer image tag from dev to latest
* Change Makefile to build images with tag latest
Change-Id: Iff074d6fe771cce48dae7190fbc69cc437138817
Signed-off-by: Sreejith Punnapuzha <sreejith.punnapuzha@outlook.com>
This adds functions for the helm-controller and source-controller from
Flux v2 [0]. The helm-controller depends on the source-controller and
so this includes a composite to wrap both. These components replace the
Helm Operator, which is now removed from the gating setup. The Helm Operator
function itself will be removed after a suitable migration period.
This also adds a format for Helm chart and Helm repository sourcing
to the versions catalog.
[0]: https://fluxcd.github.io/flux2
Closes: #372
Change-Id: I7287f1bb5b1ebd1dba9920cc0bed8c867720b4c1
Signed-off-by: Sean Eagan <seaneagan1@gmail.com>
A previous patchset was intended to accomplish a two-part substitution of
container versions into CAPI components, to work around assumptions held
by clusterctl:
(versions catalogue) --[ReplacementTransformer]--> (Clusterctl YAML)
... then
(Clusterctl YAML) --[clusterctl library]--> (CAPI manifests)
However, only the second leg (the hard part) worked right; the first part
had gaps which are fixed by this change.
This also adds the CAPD container definitions to the Clusterctl variables.
Change-Id: Ifaca46f6dd3b87c28753cd49b52e62556ead52bd
Closes: https://github.com/airshipit/airshipctl/issues/389
* Move kubeconfig from manifests/phases to the manifests/site
directory.
* Create site specific phases entry point that inherits
global phases bundle
Change-Id: I0f2893928221760e46a05630de051dd4c46c7448
Relates-To: #356
Change target cluster name for capd
provider from "dtc" to "target-cluster"
target cluster name changed at below entrypoints:
- manifests/function/k8scontrol-capd
- manifests/function/workers-capd
- manifests/site/docker-test-site
Change-Id: I72adeaf80a0d098d18e4334b02511d9917fe77b2
Change target cluster name for capo
provider from "ostgt" to "target-cluster"
target cluster name was changed at below entrypoints:
- manifests/function/k8scontrol-capo
- manifests/function/workers-capo
- manifests/site/openstack-test-site
Change-Id: I36f115e4a5debfc9c0f7e47705c87de29cf14d80
* Update CAPD manifest to inherit the clusterctl from
functions and patch just the difference which is the
infrastructure providers.
Change-Id: I0702aa6127531792df17b5ff69a2dba2242d79ac
Currently gates are broken because of the missing annotations
related to the changes of how we now invoke kustomize plugins
Related-To: #382
Closes: #382
Change-Id: I055608e361b4ac2573cc118930092760cfffcceb
New replacements provide ability to use proxy configuration for worker nodes
and workload deployment.
To use proxy the following env vars should be exported for the session when
running phases: HTTP_PROXY, HTTPS_PROXY and NO_PROXY
Make sure to define all of them, especially NO_PROXY. For example, without
adding cluster IP addresses the deployment will fail.
Change-Id: Id08126f77e0a9da31318f1a239c51a6c78a7c88e
* The phase.docEntryPointPrefix field in the metadata.yaml
allows you to define a common part of the documentEntryPoint
for all phases in the phase bundle.
For example, let metadata.yaml be
---
phase:
path: manifests/phases
docEntryPointPrefix: manifests/site/test-site
and a phase be
---
apiVersion: airshipit.org/v1alpha1
kind: Phase
metadata:
name: initinfra-ephemeral
clusterName: ephemeral-cluster
config:
executorRef:
apiVersion: airshipit.org/v1alpha1
kind: KubernetesApply
name: kubernetes-apply
documentEntryPoint: ephemeral/initinfra
Then the documentEntryPoint for executor will be prepended with
docEntryPointPrefix and the path to the executor bundle will be
manifests/site/test-site/ephemeral/initinfra
Change-Id: I29ec14378790d95b66c3ff1fe6120bb200f91a50
Relates-To: #356
Deduplicate networking definitions inside of airshipctl functions,
and make the values driveable via a catalogue.
Changes:
* Removed BMO patches at site level; drive through catalogue instead.
* Added separate entrypoints for ephemeral & target site-level.
catalogue/networking overrides. Ephemeral's kustomizes target's.
* Generalized the commonHostNetworking catalogue into a section in the
overall networking catalogue.
* Cleaned up catalogue use in general.
* Got rid of some ill-formed Type-level phase definition.
We should go back soon and define proper Type-level phases.
Change-Id: Iff96ccdcf7ebde4ae55e2b1a9d25dd1cdca0d2c8
Relates-To: https://github.com/airshipit/airshipctl/issues/315
* 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
Along with the change to support proxy configuration for control plane
there is a change for replacement transformer to support arrays of strings.
The current implementation of cloud-init configuration for the control plane
based on KubeadmControlPlane object and uses an array of strings for commands.
Change-Id: Id0a49cc1a0fdbc392c7c7a56859b21737065b0d6
