Having trouble deploying the Kubernetes Dashboard Helm chart #27
-
Hi, this is quite an exciting project! I'm not sure if this is the appropriate place to post this, but I ran into an issue when creating my first kubenix configuration with the kubernetes dashboard helm chart: { kubenix ?
let
lock = (builtins.fromJSON (builtins.readFile ../flake.lock)).nodes.kubenix.locked;
in
import (fetchTarball {
url = "https://github.com/hall/kubenix/archive/${lock.rev}.tar.gz";
sha256 = lock.narHash;
}),
system ? builtins.currentSystem
}:
(kubenix.evalModules.${system} {
module = {kubenix, pkgs, ... }: {
imports = with kubenix.modules; [
k8s
helm
];
kubernetes.helm.releases.k8s-dashboard = {
chart = kubenix.lib.helm.fetch {
repo = "https://kubernetes.github.io/dashboard/";
chart = "kubernetes-dashboard";
version = "6.0.8";
sha256 = "myLGEuL9X4yYyEbHXUMNdk+BkQ0zt0h1ybRrET5U9Xg=";
};
};
};
}) When I try to build the output I get the following error:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
looks like the default value provided by the helm char for that prop is incorrect |
Beta Was this translation helpful? Give feedback.
-
Discussions are as good a place as any! Thanks for bringing this up, @nikitawootten. As Adrian mentioned, this is because the chart is using an int here so this can be worked around by overriding the value with the corresponding string: kubernetes.helm.releases.k8s-dashboard = {
chart = kubenix.lib.helm.fetch {
repo = "https://kubernetes.github.io/dashboard/";
chart = "kubernetes-dashboard";
version = "6.0.8";
sha256 = "myLGEuL9X4yYyEbHXUMNdk+BkQ0zt0h1ybRrET5U9Xg=";
};
values.resources.limits.cpu = "2";
}; This chart has undergone quite a few changes, which includes using string values in the default branch. So this shouldn't be an issue with the next release but this still feels like a bug in kubenix as integers are valid resource values. |
Beta Was this translation helpful? Give feedback.
looks like the default value provided by the helm char for that prop is incorrect
try looking at the charts documentation to find out if you if it supports overriding default
resources
and set it to correct values ("1" for 1 cpu, or an equivalent of "1000m" etc).