Getting Started guide results in "Waiting for 1 unavailable replicas"

[mspronk]

Describe the bug

I walked through the Getting Started process as described at https://cf-for-k8s.io/docs/
Initially the cluster seems healthy, and the steps to create an organization and space are fine.

However after a few minutes, as I progress through the guide, the cluster is unhealthy.
Any cf command results in Error unmarshalling the following into a cloud controller error: no healthy upstream

Meanwhile, a resubmit of kapp deploy will show the cf-api-server and cf-api-worker as Waiting for 1 unavailable replicas. And eventually cf-api-server will disappear and only cf-api-worker remains as Waiting for 1 unavailable replicas.

Since im just 'getting started' im not too sure what too expect, but this seems to behave very flakey without doing anything beyond the introductory guide.

To Reproduce

Steps to reproduce the behavior: Walk through the Getting Started guide on a fresh install.

Expected behavior

The cluster should remain running and intact

Additional context

CLI versions

Ubuntu Server 20.04.3
Docker 20.10.2

AMD Ryzen 7 (8 core)
64GB DDR4

1. ytt --version: 0.35.1
2. kapp --version: 0.37.0
3. kubectl version: Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T21:04:39Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
   Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-03-11T06:23:38Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
4. cf version: 7.2.0+be4a5ce2b.2020-12-10
5. kind 0.11.1

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/179030221

The labels on this github issue will be updated when the story is started.

[mspronk]

FYI I've tried the same on a fresh new VM with Ubuntu 20.04 server installed, and am experiencing the exact same problems, so it is definitely reproduceable.