We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uptes is getting suck in endless evaluation loop in cases when standard core Namespace is part of the test example material.
Namespace
For example, if
apiVersion: v1 kind: Namespace metadata: name: test-namespace
is getting applied by uptest, then the test run will timeout on the following condition:
case.go:363: command "$***KUBECTL*** wait namespace./test-namespace --for=condition=Ready --timeout 10s"
Add Namespace to your uptest example
Implement the similar skipping logic, see Secrets handling PR upbound/official-providers-ci#37
The text was updated successfully, but these errors were encountered:
Hande Namespace v1 in the uptest run
3d6ee34
* Special skip of the Namespace object similar to Secret * Fixes crossplane#18 Signed-off-by: Yury Tsarev <[email protected]>
Handle Namespace v1 in the uptest run
be9fe26
Successfully merging a pull request may close this issue.
What happened?
Uptes is getting suck in endless evaluation loop in cases when standard core
Namespace
is part of the test example material.For example, if
is getting applied by uptest, then the test run will timeout on the following condition:
How can we reproduce it?
Add Namespace to your uptest example
What environment did it happen in?
Possible solution
Implement the similar skipping logic, see Secrets handling PR upbound/official-providers-ci#37
The text was updated successfully, but these errors were encountered: