feat: K8sFlavour #161
No reviewers
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: NationTech/harmony#161
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/detect_k8s_flavour"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Added K8sFlavour to K8sAnywhereTopology to be able to store and use the underlying Kubernetes implementation
@ -49,1 +49,4 @@
#[derive(Debug, Clone)]
pub enum K8sFlavour {
Okd,
Should be OpenshiftFamily(Version) as we want the same behavior between okd and openshift.
@ -177,0 +210,4 @@
version
.git_version
.contains("k3s")
.then_some(K8sFlavour::K3d)
That is a clear naming problem. Should be either k3d for real by detecting it another way or k3sFamily just like OpenshiftFamily
@ -177,0 +220,4 @@
&& !version.git_version.contains("k3s")
&& !version.git_version.contains("k3d")
{
Some(K8sFlavour::K8s)
This is more of a fallback to a default than a true way to detect that we're running vanilla k8s (made by kubeadm for example).
Should be called Default or Fallback or Unknown but not k8s.