When using --additional-trust-bundle argument, user-ca-bundle ConfigMap is created before the actual namespace it lives in.

    4.17

    Don't create the "clusters" namespace, and create a cluster with --additional-trust-bundle

    hypershift create cluster openstack --openstack-ca-cert-file ~/hypershift/cacert --openstack-credentials-file ~/hypershift/clouds.yaml --openstack-external-network-name hostonly --base-domain example.com --infra-id openstack --name openstack --ssh-key ~/hypershift/id_rsa.pub --pull-secret ~/hypershift/pull-secret.json --release-image registry.build03.ci.openshift.org/ci-ln-2vlyrz2/release:latest --openstack-node-image-name rhcos-4.17 --openstack-node-flavor m1.xlarge --node-pool-replicas 1 --control-plane-operator-image quay.io/emilien/hypershift:openstack-support --additional-trust-bundle ~/hypershift/cacert
2024-07-10T16:14:43-04:00	ERROR	Failed to create cluster	{"error": "failed to apply object \"clusters/user-ca-bundle\": namespaces \"clusters\" not found"}
github.com/openshift/hypershift/cmd/cluster/openstack.NewCreateCommand.func1
	/home/emilien/git/github.com/shiftstack/hypershift/cmd/cluster/openstack/create.go:220
github.com/spf13/cobra.(*Command).execute
	/home/emilien/git/github.com/shiftstack/hypershift/vendor/github.com/spf13/cobra/command.go:983
github.com/spf13/cobra.(*Command).ExecuteC
	/home/emilien/git/github.com/shiftstack/hypershift/vendor/github.com/spf13/cobra/command.go:1115
github.com/spf13/cobra.(*Command).Execute
	/home/emilien/git/github.com/shiftstack/hypershift/vendor/github.com/spf13/cobra/command.go:1039
github.com/spf13/cobra.(*Command).ExecuteContext
	/home/emilien/git/github.com/shiftstack/hypershift/vendor/github.com/spf13/cobra/command.go:1032
main.main
	/home/emilien/git/github.com/shiftstack/hypershift/main.go:78
runtime.main
	/home/emilien/sdk/go1.22.0/src/runtime/proc.go:271
Error: failed to apply object "clusters/user-ca-bundle": namespaces "clusters" not found
failed to apply object "clusters/user-ca-bundle": namespaces "clusters" not found

    no error

    When creating the namespace manually and recreating the cluster, we can confirm the ordering issue:

2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "ConfigMap", "namespace": "clusters", "name": "user-ca-bundle"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "Namespace", "namespace": "", "name": "clusters"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "Secret", "namespace": "clusters", "name": "openstack-pull-secret"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "Secret", "namespace": "clusters", "name": "openstack-ssh-key"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "", "namespace": "clusters", "name": "openstack"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "Secret", "namespace": "clusters", "name": "openstack-cloud-credentials"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "Secret", "namespace": "clusters", "name": "openstack-etcd-encryption-key"}
2024-07-10T16:23:04-04:00	INFO	Applied Kube resource	{"kind": "NodePool", "namespace": "clusters", "name": "openstack"}