Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Present readiness check for controller fails in case auth or tls is enabled #417

Closed
Prabhaker24 opened this issue Jul 6, 2020 · 0 comments · Fixed by #418
Closed

Present readiness check for controller fails in case auth or tls is enabled #417

Prabhaker24 opened this issue Jul 6, 2020 · 0 comments · Fixed by #418
Assignees
@Prabhaker24

Comments

@Prabhaker24
Copy link
Contributor

Description

Present readiness check for controller fails in case auth or tls is enabled

Importance

must_have

Location

changes are needed in pkg/util/pravegacluster.go

Suggestions for an improvement

Readiness check should be changed in case auth is enabled or it's is enabled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Prabhaker24 Prabhaker24

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 417: Added readiness check for auth and tls pravega/pravega-operator
1 participant
@Prabhaker24