|
|
|
|
|
by mroche
2402 days ago
|
|
What difficulty (or subpar experience) are you running into with CRC? Initially it was a bit weird, but getting up and running is fairly simple. 1) Go to Red Hat’s cloud site (linked on GitHub) and download the latest CRC release and your pull secret. This does require having at least an empty Red Hat account, which may bother some. 2) Extract the release and run `crc setup` and let it do it’s thing. 3) Run `crc start -p /path/to/pull/secret` and wait for it to finish getting up and running. First time this may take 10 minutes, follow up starts 4. You can pass other options as well as needed. 4) Run `eval $(crc oc-env)` and start working with developer:developer credentials (or the provided kubeadmin creds). Use `crc console` to get to the WebUI. We use this on Linux and macOS here just fine for local development and testing. As always, though, YMMV. CRC still has some other quirks that need to be ironed out, but it is generally useable. So far for us the weird parts are the limited self-signed certs and lack of cluster metrics, but both are known issues to the project. And that you can’t have a VPN process running as the startup will restart network services on your system. |
|