Commit 18095de
committed
feat: implement managed control planes
Cluster template now has
```
managed:
enable: true|false
```
configuration in the control planes model.
Creating managed control planes will be possible only if the Omni
account is configured with the provider to use for managed control
planes, otherwise resource validation won't allow creating the machine
set with such configuration.
Also drop `MachineRequestSet` allocation mode from the machine set,
remove source there, as it doesn't make much sense: for managed control
planes it should always use the machine request set name with the same
name as the machine set.
Config patches for managed mode are going to be added in the follow-up
PRs.
Fixes: #705
Signed-off-by: Artem Chernyshev <artem.chernyshev@talos-systems.com>1 parent e4586f4 commit 18095de
File tree
48 files changed
+2752
-4897
lines changed- client
- api
- common
- omni
- management
- oidc
- resources
- specs
- pkg
- omni/resources/omni
- template
- internal/models
- operations
- testdata/export
- testdata
- cmd/omni/cmd
- frontend
- src
- api
- omni/specs
- states/cluster-management
- views
- cluster/ClusterMachines
- omni/Clusters/Management
- test/unit
- internal
- backend/runtime/omni
- controllers/omni
- internal/machineset
- pkg/config
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
48 files changed
+2752
-4897
lines changedSome generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments