Closed kenorb closed 3 years ago
Have you tried quoting it?
Have you tried quoting it?
Quoting the value seems to work fine:
TASK [xanmanning.k3s : Ensure k3s config file exists] *********************************************************************************************************************************************************************************
--- before: /etc/rancher/k3s/config.yaml
+++ after: ~/.ansible/tmp/ansible-local-14182803vupoye/tmp5usv3qnl/config.yaml.j2
@@ -8,5 +8,5 @@
-write-kubeconfig-mode: 644
+write-kubeconfig-mode: '0640'
Thank you.
To avoid confusion and copy-paste errors, the following resources needs to be updated:
Summary
I was confused by
write-kubeconfig-mode
when I set to:then it become
416
.And when setting
0644
, it becomes420
.Normally when you do 0640 with
chmod
command it works fine.Is that expected behaviour?
Issue Type
Controller Environment and Configuration
Steps to Reproduce