17 Коммитов

Автор	SHA1	Сообщение	Дата
Amber Brown	e711e610a0	Move to maintained yaml lib (#3454) ... * move to maintained yaml lib * update validate-imports * go mod	2024-07-10 09:57:42 +10:00
Amber Brown	e15e78c719	Remove initial installer dependencies (#2842)	2023-06-01 14:30:16 +10:00
bennerv	c0452ecb82	Update user admin kubeconfig generation to happen every 3 months minimum	2023-02-09 17:58:38 -05:00
darthhexx	4fba704abb	Found a cleaner way to ignore the unknown fields	2023-02-02 08:12:55 +01:00
Amber Brown	766cc5f1b0	move installtime set to startInstallation rather than in the middle of kubeconfig generation	2022-06-08 11:58:50 +10:00
Leszek Jakubowski	03b4070625	added more unit tests, changed arg of checkUserAdminKubeconfigUpdated	2021-11-15 15:42:33 +00:00
Leszek Jakubowski	0abd50c938	Update pkg/cluster/kubeconfig_test.go, simplify data structure around user kubeconfig ... Co-authored-by: Mikalai Radchuk <509198+m1kola@users.noreply.github.com>	2021-11-15 15:42:33 +00:00
Leszek Jakubowski	cf3bc17679	fixing user admin kubeconfig api-int to api on PUCM	2021-11-15 15:42:33 +00:00
Roland Kunkel	faf3d39c7b	move generateKubeconfigs to kubeconfig.go	2021-07-20 17:30:03 +02:00
Mangirdas Judeikis	3d95bffcb1	Add API generation for kubeconfig	2021-06-08 13:16:08 +01:00
Jim Minter	d68fda1888	noop fixup imports	2021-03-02 13:17:01 -06:00
Jim Minter	9926686bb0	pull graph into new subpackage of cluster	2021-02-23 11:38:47 -06:00
Jim Minter	17df52a95c	separate graph and persistedGraph ... We are running into trouble where we can't straightforwardly unmarshal old cluster graphs (the serialisation of some ignition structs has changed enough to break unmarshalling). Fundamentally the issue is that the installer does not intend for the graph to be a stable persisted API, which is fair enough, but it makes this hard to fix. Separate graph and persistentGraph: * graph is a one-time object: create it, resolve it, persist it, done. * persistedGraph can be read subsequently and, with care, potentially round-tripped if necessary. Callers of persistentGraph.get() receive any errors when unmarshalling the object that interests them, so they are forced to handle it. Using json.RawMessage also has the side effect that we shouldn't be at as much risk of accidentally losing data if we ever needed to round-trip the graph.	2021-02-15 11:05:17 -06:00
Jim Minter	57bba81ac3	add system:aro-sre kubeconfig	2020-12-09 16:22:50 -06:00
Jim Minter	7e39957e07	enable graph to round-trip unknown values	2020-12-09 16:22:50 -06:00
Nils Elde	79d78250b2	rename i to m	2020-10-01 10:03:12 -04:00
Amber Brown	491940a47f	install/Installer -> cluster/manager	2020-08-24 20:32:21 +10:00