-
Notifications
You must be signed in to change notification settings - Fork 69
CON-3113 - Implementation of probes for NFS deployments #439
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.
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
Conversation
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
…to new-nfsprobe
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
dileepds
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
datamattsson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we leaving residual serviceAccounts, roles and roleBindings around? I can't see these being pruned in deleteNFSResources.
pkg/flavor/kubernetes/nfs.go
Outdated
| livenessProbe := &core_v1.Probe{ | ||
| ProbeHandler: core_v1.ProbeHandler{ | ||
| Exec: &core_v1.ExecAction{ | ||
| Command: []string{"/bin/sh", "/nfsHealthCheck.sh", "3", name, nfsNamespace}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we maintain a hash of actions for the 1, 2 and 3 in the script instead? I find this numbering very counter-intuitive. nfsNamespace is not being used in the script and should be removed.
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
Signed-off-by: AnushaY1916 <anuanusha471@gmail.com>
Signed-off-by: Michael Mattsson <michael.mattsson@gmail.com>
datamattsson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, can we please work #437 next?
No description provided.