sparse-intern-71089
01/10/2023, 6:53 PMsquare-laptop-45713
01/10/2023, 6:56 PM~ kubernetes:core/v1:Secret ***/***-dev-***-jobservice refreshing (0s)
kubernetes:core/v1:Secret ***/***-dev-***-jobservice (0.00s)
~ kubernetes:core/v1:ConfigMap monitoring/prometheus-server refreshing (0s)
kubernetes:core/v1:ConfigMap monitoring/prometheus-server (0.00s)
~ kubernetes:core/v1:Secret ***/***-dev-***-core refreshing (0s)
kubernetes:core/v1:Secret ***/***-dev-***-core (0.00s)
~ kubernetes:core/v1:Secret ***/***-dev-***-registry refreshing (0s)
kubernetes:core/v1:Secret ***/***-dev-***-registry (0.00s)
square-laptop-45713
01/10/2023, 6:57 PM@ Refreshing....
kubernetes:core/v1:ConfigMap ***/***-dev-***-registry (8s)
kubernetes:core/v1:Secret ***/***-dev-***-trivy (9s)
kubernetes:core/v1:ConfigMap ***/***-dev-***-jobservice-env (9s)
billowy-army-68599
square-laptop-45713
01/10/2023, 7:50 PMbillowy-army-68599
square-laptop-45713
01/10/2023, 7:58 PMkubectl apply
square-laptop-45713
01/10/2023, 7:58 PMbillowy-army-68599
helm.Release
or helm.Chart
?billowy-army-68599
square-laptop-45713
01/10/2023, 8:07 PMhelm.Chart
square-laptop-45713
01/10/2023, 8:07 PMsquare-laptop-45713
01/10/2023, 8:24 PMhelm.Release
is delegating to the helm binarysquare-laptop-45713
01/10/2023, 8:25 PMhelm.Chart
to a helm.Release
in my IaC it will redeploy everything?square-laptop-45713
01/10/2023, 8:26 PMsquare-laptop-45713
01/11/2023, 12:14 AMhelm.v3.Chart
does not take into account the version of k8s of the cluster since the template in the Chart I have has different rendering depending on .Capabilities
based on available API resource versions. Is there a way either through the kubernetes.Provider
or helm.v3.Chart
to tell the command what version of k8s to use for rendering?