Question: is there anything i need to do for the mount path?

Asked By
blaw2422
Asked At
2018-04-24 05:20:39

Found 15 possible answers.

User Answered At Possible Answer
andyzhang 2018-04-24 05:23:17 mount path is correct
blaw2422 2018-04-24 05:26:13 use kubespray to bootstrap cluster. anything I need to enable?
andyzhang 2018-04-24 05:28:27 I am not familiar with kubespray, what's your agent node OS? sudo mount -t cifs //ACCOUNT-NAME.file.core.windows.net/SHARE-NAME test -o vers=3.0,username=ACCOUNT-NAME,password=ACCOUNT-KEY,dir_mode=0777,file_mode=0777,sec=ntlmssp mkdir test to narrow down this issue, you may try mount azure file on agent node first
blaw2422 2018-04-24 05:33:50 oh cool - it fails much appreciated i gotta run, but I've got a good starting point for tomorrow. thanks a lot for the help thats good news...kinda
andyzhang 2018-04-24 05:38:33 In Ubuntu, you should install "sudo apt-get install cifs-utils" first
mark-nb 2018-04-24 08:39:57 ok, thanks for the follow up.Will leave the useCCM to false for now
eamon824 2018-04-24 09:18:01 Tested acs-engine 0.16.0 with k8s 1.9.7 there and had an issue in westurope around port-forwarding: kubectl run -i --tty busybox --image=busybox -- sh <@eamon824> uploaded a file: Untitled and commented: As an fyi, acs-engine upgrade from 1.9.3 to 1.9.7 worked fine for the masters but timed out when recreating the first worker node (see error message above - fairly no descript). Re-running acs-engine worked fine. Tried the exact same setup in eastus and it worked fine. Error attaching, falling back to logs: error dialing backend: dial tcp: lookup k8s-agentpool1-19302961-1 on 168.63.129.16:53: no such host If you don't see a command prompt, try pressing enter.
joebeau93 2018-04-24 13:11:24 Will ACS-Engine Created clusters be "not supported" when they get rid of ACS in favor of AKS?
eamon824 2018-04-24 13:46:41 Anyone come across this before? Perhaps co-incidence but happened after an acs-engine upgrade. Warning ProvisioningFailed 57s (x42 over 11m) persistentvolume-controller Failed to provision volume with StorageClass "default": azureDisk - account ds8d69632747ad11e89ee80 does not exist while trying to create/ensure default container
rulrich 2018-04-24 13:54:40 @joebeau93 get rid of acs?
SLACK 2018-04-24 13:55:40 @rulrich commented on @eamon824 ’s file Untitled https://kubernetes.slack.com/files/U7ZMALE30/FAC1KH02F/-.txt : So you reran the same exact upgrade sequence again?
eamon824 2018-04-24 13:56:13 Yea, idempotent, so just skips what it's already done.
rulrich 2018-04-24 13:56:38 Interesting that it do ant just retry the failed step during the first run
eamon824 2018-04-24 13:57:54 yea idk... new learning I just found is that with auto-scaling enabled, appears the new nodes created still use the old k8s version.
rulrich 2018-04-24 14:00:32 The workers? Or masters as well?

Related Questions