bradleyd
commented
1 year ago Hey @AnnuCode, thanks for reading my book!
I have not tried codespace so I am not sure how all this would work. The great thing about concepts like Infrastructure as code and configuration management is they can be applied to any host/cloud provider and it should always just work. Now you will have to do some changes as this book was intended to walk you through a specific scenario to teach you these concepts. Here are some quick thoughts:
- From the sounds of it the Vagrant commands (infrastructure as code) would not be useful for codespace vm. However, ansible is triggered during the provision phase in vagrant.
- After the VM is up and running, you can run the ansible-playbook command directly but would need to create a hosts (inventory) file that points to the VM instead of localhost.
- The vagrant Vbox setup creates a separate IP used throughout the book, you would just need to make sure you are using the one from codespace instead.
- Section II might be more difficult as the instructions expect minikube locally. It can be done but you will need to take care on IP addresses and proxying Kubernetes commands and service.
If you end up getting it to work, feel free to open a PR with a how to for codespace.
Good luck!
Hi @bradleyd , is there a way we can code along on Codespace while reading this book? Codespace provides a VM so I think there is no need for VirtualBox? Also, instead of running Vagrant commands, should I run Ansible commands (like
ansible playbook) directly? Can we configure the Codespace VM in some way to set it up for following the code samples(something similar was done in the Apple Silicon Qemu case)? Any suggestions will be helpful, thank you.