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
CreateAndWaitUntilReady method in daemonset package uses conditions field which is optional.
eco-goinfra/pkg/daemonset/daemonset.go
Line 290 in 8f863fc
Line 313 in 8f863fc
Whereas, IsReady method uses desired pod count == ready pod count
Line 372 in 8f863fc
Line 395 in 8f863fc
We are not able utilise CreateAndWaitUntilReady method because conditions field is not getting populated. https://docs.openshift.com/container-platform/4.15/rest_api/workloads_apis/daemonset-apps-v1.html#status
Wondering if we have any particular reason to use conditions field ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
CreateAndWaitUntilReady method in daemonset package uses conditions field which is optional.
eco-goinfra/pkg/daemonset/daemonset.go
Line 290 in 8f863fc
eco-goinfra/pkg/daemonset/daemonset.go
Line 313 in 8f863fc
Whereas, IsReady method uses desired pod count == ready pod count
eco-goinfra/pkg/daemonset/daemonset.go
Line 372 in 8f863fc
eco-goinfra/pkg/daemonset/daemonset.go
Line 395 in 8f863fc
We are not able utilise CreateAndWaitUntilReady method because conditions field is not getting populated.
https://docs.openshift.com/container-platform/4.15/rest_api/workloads_apis/daemonset-apps-v1.html#status
Wondering if we have any particular reason to use conditions field ?
The text was updated successfully, but these errors were encountered: