stackabletech / stackabletech/issues
Operators become ready before the CRD has been installed
Open
@xeniape is already working on this.
Since Aug 11, 2026.
type/bug
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This leads to errors as seen in getting_started scripts (described in a slack thread):
Creating Airflow cluster
error: resource mapping not found for name: "airflow" namespace: "" from "airflow.yaml": no matches for kind "AirflowCluster" in version "airflow.stackable.tech/v1alpha1"
ensure CRDs are installed first
The workaround is to add a sleep 20
Why now
Previously, Helm installed the CRDs, and did so before deploying the operators.
Now Helm deploys the operators without CRDs (by default), and the CRDs are created after the operator pod is up. An apply of a CR that happens straight after that but before the maintainer has created the CRD will fail.
Possible solution
Add a startupProbe endpoint which only gives 200 OK when the CRD has been deployed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.