v0.7.0

• When we push changes to the branch, go-git logs a message by default : it contains link to create PR against the upstream repository (Obmondo's kubeaid-config). I need to take a look at whether we can disable this or not.

• At the end of the cluster setup process, print out a help text for the user : containing command which the user can just copy paste and then visit localhost:8080 to access the ArgoCD dashboard.

• Have a flag, which can be used to make the script push changes directly to the main branch instead of going through the PR flow (this should be used while testing only).

• Have a --skip-monitoring-setup flag, to skip KubePrometheus installation.

• Use a dedicated K3D container image registry

• During cluster setup phase, install ArgoCD and Sealed Secrets using KubeAid's charts and not direct upstream's charts

• ArgoCD App file name format changed from*.app.yaml to *.yaml.
  Helm chart values file name format changed from*.values.yaml to values-*.yaml.

• --debug flag works.

• time slog attribute will be present only in debug mode.

• Fix CI build failure by doing :

	// We need this, otherwise Github Actions CI run will fail with this error :
	// https://github.com/Obmondo/kubeaid-bootstrap-script/actions/runs/14102269130/job/39500847660#step:6:5993.
	// REFER : https://github.com/argoproj/argo-cd/issues/22007.
	github.com/cyphar/filepath-securejoin => github.com/cyphar/filepath-securejoin v0.3.6

• colored logger

Azure specific work done :

• Azure Workload Identity + ClusterAPI setup

  A small task is still remaining. I need to change a command, so az login can be done non-interactively.

v0.6.0

Features :

• Added a command to provision a local K3D cluster and setup KubeAid (for internal testing purposes).

• This is the priority of cloud credentials sources :
  CLI flags > Environment Variables > Config file > ~/.aws

• (aws) : add controlPlane.loadBalancerScheme option in config

• You can now specify the KubeAid tag you want to use, in the config file.

Fixes :

• retry locating chart on server misbehaviour error

v0.5.0

Features

• Syncing all ArgoCD apps at the end of the cluster bootstrap process

• Added support for specifying additional users | Inferring VM specs from the specified type, for each node-group | Codebase refactoring

• Complete cluster upgrade implementation (supporting only AWS for now) | Adding HCloud support (tested)

• Successfully provisioning a cluster in Hetzner Cloud

• Add a command to spin up a dev environment

Chores

• Writing short help message for each leaf CLI command | Fixing Makefile | Small README.md updates

• Removing replicas field for a node-group

• Solved last 2 issues mentioned in issue #25

• Update AWS specific sample Kubeaid Bootstrap Script config file

Fixes :

• Removing monitoring namespace from cluster-vars.jsonnet.tmpl, so that Prometheus doesn't monitor itself

• Fix Disaster Recovery Setup : Link IAM Role and Policy

• Managing ClusterAPI components versions in KubeAid and not here

• Replacing the skip-kubeaid-config-setup flag with skip-kube-prometheus-build flag

• Checking out to default branch when repo already exists | Proper error handling while creating IAM Roles and Policies

• Creating Cilium ArgoCD App and corresponding values file when kubeaid-config gets updated post cluster provisioning

---

Corresponding changes done in KubeAid

• Limited the Infrastructure Provider component's cache to its own namespace.

• Updated ClusterAPI version.

• Fixed scale from 0 support.

• Fixed kubeaid-bootstrap-script #41

Hetzner specific updates :

• Added support for provisioning clusters in Hetzner Cloud (tested).

• Restructured the capi-cluster/hetzner subchart, keeping in mind that we want to mix Hetzner bare-metal and HCloud in the future.

• Fixed postKubeadm commands, which were causing HCloud cluster provisioning to fail.

• Updated ClusterAPI provider Hetzner version.

AWS specific updates :

• Allowing the user to specify the control-plane Loadbalancer scheme.

• Distributing a node-group across multiple Failure Domains (Availability Zones) for high-availability.

• Making it mandatory for the user to specify the min and max size explicitly for each node-group.

• Setting PUT HTTP response hop limit to 2, supporting both IMDSv1 and IMDSv2.

• Using hostNetwork for AWS CCM. Otherwise the NoCredentialsProvider error pops out after some time.

• Added support for specifying additional users, each with their corresponding SSH public key.

• Fixed Sealed Secret keys backuper container image and ServiceAccount name

• Updating part 1 of the KubeAid demonstration blog series for AWS

Ignore changes in the capi-cluster/azure subchart and hetzner-failover-script. They are untested anyways.

v0.4.0

AWS :

• enableAuditLogging option in the config to do the KubeAPI audit-logging setup on behalf of the user.

• Switching from (temporary) credentials to IAM roles after cluster bootstrap.

• Allowing the user to specify extraArgs and extraVolumes to the KubeAPI server, extra files for the master nodes.

• Updated CAPI Operator and Providers versions. Did necessary changes in the Script as well as KubeAid to fix issues caused by breaking changes.

• Added scale to / from zero support for node-groups.

• Supporting retrial mechanism when clusterctl move has already been executed

• Installing Sealed Secrets in the sealed-secrets namespace (in the provisioned cluster, when syncing the sealed-secrets ArgoCD App)

• Fix sealed-secrets backuper IAM policy

Hetzner :

• Hetzner Failover Script cleaned up and moved here from the dockerfiles repo.

Support Cluster API - Cluster AutoScaler integration

• Support Cluster API - Cluster AutoScaler integration

• Fixing Cluster AutoScaler ArgoCD App template file name

• Removing CAPI and CAPA versions from capi-cluster.values.yaml template

Support specifying machinepool labels and taints

• Adding support for specifying MachinePool labels and taints in the KubeAid Bootstrap Script config file

v0.1.0

Merge pull request 'Linking to KubeAid demo (Part 1) blog in KubeAid'…