-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fix kubectl logs for init containers #27042
Conversation
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
2 similar comments
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
@@ -2845,6 +2845,10 @@ func (kl *Kubelet) validateContainerLogStatus(podName string, podStatus *api.Pod | |||
var cID string | |||
|
|||
cStatus, found := api.GetContainerStatus(podStatus.ContainerStatuses, containerName) | |||
// if not found, check the init containers |
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.
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.
This one fixes the issue of pulling init container's log. Not addressed #27040.
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.
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.
@dchen1107 what is a init container logs
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.
@krmayankk see here #23666
LGTM cc/ @smarterclayton |
Also Lgtm, thanks |
The failure has nothing to do with this pr. Reapply lgtm |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
1 similar comment
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
@lukaszo thanks for the pointer, this feature looks very interesting and usable. Can someone also point to examples of how to use it ? I very often see the PR for new features get merged without an example in the docs/user guides or contrib. It would help to make that as requirement for these new PR merges imho |
@krmayankk init containers are for example used in petsets https://github.com/kubernetes/contrib/blob/master/pets/mysql/galera/mysql-galera.yaml#L32-L76 |
We definitely want people to try alpha features, but they're also somewhat alpha and subject to change. We'll probably have some core documentation for petset but I would expect them to change in 1.4 as we learn more about what we need to implement. |
@smarterclayton so, are we going to move this feature to 1.4 milestone? |
Not sure what you're asking? I had no plans to move this PR out of v1.3 since it's contained, reviewed, and has been in the queue for a few days. |
@smarterclayton are P3 PRs still merged? |
Anything in the queue is being left in the queue - we may decide to cut the RC without everything in the queue being merged but that decision hasn't been made. This also probably isn't a P3. |
This is P1 because it would block debugging of pet sets for end users. We can kick it to P2 if necessary, but I'd be more concerned without this than with other PRs related to init containers. |
GCE e2e build/test passed for commit 07d13c1. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 07d13c1. |
Automatic merge from submit-queue |
Related issues: #25818 #27040