Bich C. Le
Bich C. Le
We need an integration test to regression test the main features of arlon: - cluster creation from base cluster, with optional profile - applying a profile to a base cluster...
When a user pushes a change to a base cluster that affects fields that CAPI providers treat as immutable, such as the `instanceType` or `additionalTags` of the AWSMachineTemplate spec, then:...
CAS is supported for current-gen clusters via flags and the Helm chart which provisions CallHomeConfig resource if needed. This is for porting that work to next-gen clusters. Note that this...
An ApplicationSet allows a single application to target multiple clusters. This may help with the update problem (#7) Aha! Link: https://pf9.aha.io/features/ARLON-171
Today we tag, version, publish binaries, and publish images in a manual way. We need to document and automate as much as possible a release process. Use existing OSS projects...
This may involve adding a new ApiProvider property to the clusterspec object. Aha! Link: https://pf9.aha.io/features/ARLON-170
Now that arlon supports CAPI-AWS-kubeadm clusters, the issue of CNI came up. A CAPI kubeadm cluster starts with no CNI, so any bundles that install workloads (e.g. applications) will be...
In 0.9.x + ("next-gen" and beyond), rethink how bundles and profiles should be represented and manipulated. A few thoughts: - Try to get rid of the "compiled" component in git...
The current "manage external cluster" feature was designed with gen1 (0.3.x) profiles. If profiles are redesigned in a significant way in v0.9.x (see issue #20), then this feature will need...
Arlon and ArgoCD apply CAPI manifests "as is". The user is fully responsible for the manifest contents. Examples of bad things that can happen: - It's not always intuitive to...