-
Notifications
You must be signed in to change notification settings - Fork 40
Some powershell commands in the "How to Run the OSM Manual Demo" dont work #66
Comments
@apoutney , the commands that are failing for you are to be run on a Unix (or similar) shell. These aren't powershell commands, so running them on powershell are going to fail. |
We should update the demo to be powershell friendly. |
@shashankram, thanks for the clarification :). I hadnt seen anywhere in the documentation that suggested they Unix shell commands. Since kubectl is just the cli I assumed they would work in powershell |
@shashankram Does the doc need to be updated with a title UNIX as suggested above? |
The prerequisites mentions this: Does that suffice? |
TBH: I'm not sure if its the documentation that is wrong or if its something in my environment or if there is an issue with the commands.
I have been following the "How to Run the OSM Manual Demo" and have encountered some issues
First, in the section "Create the Bookstore Application Namespaces" the following script is supplied
for i in bookstore bookbuyer bookthief bookwarehouse; do kubectl create ns $i; done
However this results in the following error:
I managed to get around this by creating the namespaces individually.
But then in the "Verify the Traffic Policy Mode" the following command is given:
kubectl get configmap -n osm-system osm-config -o json | jq -r '.data["permissive_traffic_policy_mode"]'
This produces the following error:
I again managed to get around this, by using the kubectl describe command on the config map to check the permissive_traffic_policy_mode value.
Then, in the section "Permissive Traffic Policy Mode" the following command is given to update the config map:
kubectl patch ConfigMap osm-config -n osm-system -p '{"data":{"permissive_traffic_policy_mode":"true"}}' --type=merge
But again this doesnt work and responds with the following error:
Is it the documentation that is wrong? Or have I missed something?
The text was updated successfully, but these errors were encountered: