Fleet Management
Fixed
- Exclude
crossplane which consists of many deployments.
Changed
- Updated CAPA template output to support new subnet layout as of cluster-aws v0.21.0
- Change default folder for cluster base templates generated by
gitops add base from bases/clusters/<PROVIDER> to bases/clusters/<PROVIDER>/template
Added
- Add default machine pool name for
gitops add base generated templates to capa and gcp (CAPG) providers with value: machine-pool0
Changed
- Adjusted communication with Dex in the
login command to provide an option to choose from multiple connectors - Modified detection of installation providers - downloading the provider information from Athena with a fallback to the old detection from API URLs
- Added a new provider -
cloud-director
Added
- Introduced a new
--connector-id flag in the login command to specify a Dex connector to use and skip the selection step - Ensured that ID tokens needed for OIDC authentication are renewed only when they expire
Added
- Added a new crossplane specific controller,
crossplaneauth. It detects when a ClusterRole crossplane-edit is created
(which means crossplane is installed with its rbac-manager and binds default:automation SA and customer’s admin
user group to this ClusterRole.
Changed
- Fix
pods/log policy rule.
Added
- Add flags
--cluster-type, --https-proxy, --http-proxy, --no-proxy, --api-mode, --dns-mode, --vpc-mode and `–topol - ogy-mode
totemplate clusterthat specifycapa` as provider. - Add
gitops add base command to generate CAP[A,G,O] bases. The values for --provider flag is compatible with the template cluster command (A: capa, G: gcp, O: openstack).
Changed
- Increased memory limits for updater, recommender and admissionController
Changed
- Extended detection of providers in the login command to take the provider value primarily from Athena with fallback to the original way of inspecting the API URL
Fixed
- Respect
--control-plane-instance-type for AWS cluster templating. Previously, the default value m5.xlarge was always used.
