Quickstart install procedure 2.0 (SpaceOne initialization) #148
Unanswered
Cclleemm
asked this question in
Bug Report
Replies: 1 comment
-
In Step5, you have to execute command in spacectl POD. Log-in by "kubectl exec -ti spacectl-xxxxxxxxx -n cloudforet -- /bin/bash" |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have a suggestion for your quickstart documentation (on Minikube for the v2) because I can't deal with the part 5) Default Initialization (in spacectl POD) section.
You change the way to initialized spaceone (cloudforet-io/cloudforet-io.github.io@a03adcb#diff-24a3379e185f0ea2913321a4983425e14b4eb3cddba4e7bc2500c1b5ed3a826bR154) but I can't understand the link between the step :
spacectl config init -f default.yaml
and
root domain yaml file (root.yaml)
The root.yaml is not created automatilly, if we have to create it manually can you specified it in the doc ?
However I tried to create it with this payload
But when I run
spacectl exec init identity.System -f root.yaml
I have the following error messageBeta Was this translation helpful? Give feedback.
All reactions