Tim Hockin
e9dd8a68f6
Revert k8s.gcr.io vanity domain
...
This reverts commit eba5b6092ahttps://github.com/kubernetes/kubernetes/issues/57526
2017-12-22 14:36:16 -08:00
Tim Hockin
eba5b6092a
Use k8s.gcr.io vanity domain for container images
2017-12-18 09:18:34 -08:00
Kubernetes Submit Queue
ebd3d68039
Merge pull request #55831 from Random-Liu/rename-log-dump-env
...
Automatic merge from submit-queue (batch tested with PRs 55392, 55491, 51914, 55831, 55836). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md ">here</a>.
Rename log-dump env to `LOG_DUMP_SYSTEMD_SERVICES`.
For https://github.com/kubernetes/features/issues/286 .
Rename `SYSTEMD_SERVICES` to `LOG_DUMP_SYSTEMD_SERVICES`. test-infra disables log dump in our e2e framework, and uses a different log dump logic https://github.com/kubernetes/test-infra/blob/master/kubetest/e2e.go#L480-L497 . So the flags we added in https://github.com/kubernetes/kubernetes/pull/55288 will not work in test-infra.
Fortrunately, test-infra is using the same script `cluster/log-dump/log-dump.sh`, so we could still configure systemd services by setting the environment variable globally.
The original environment variable name is too general for setting globally, change it to a more specific name.
**Release note**:
```release-note
none
```
2017-11-17 00:18:25 -08:00
Lantao Liu
0085e2208d
Rename log-dump env to LOG_DUMP_SYSTEMD_SERVICES.
2017-11-16 00:41:27 +00:00
Marcin Owsiany
310ab8c3c4
Do not crash on empty NODE_NAMES array.
2017-11-14 14:43:30 +01:00
Lantao Liu
32c4295bcf
Support collecting log for alternative container runtime in e2e test.
2017-11-10 18:46:48 +00:00
Davanum Srinivas
9a217217c1
Fix log collection for kubeadm-gce tests
...
Separate out kuberenetes-anywhere provider under cluster/ but
delegate all the functionality to the "gce" one since the code
would be the same. Except for the name of the node, the
NODE_INSTANCE_PREFIX will be different, so account for that.
2017-10-26 07:57:42 -04:00
zouyee
5f9d931804
[cluster/log-dump] bump daemonset version
2017-10-24 10:30:20 +08:00
Jordan Liggitt
d7699028f6
Include audit log in master log capture
2017-09-24 19:59:53 -04:00
Shyam Jeedigunta
6ae0eb8806
Fix bug with gke in logdump
2017-09-13 14:03:03 +02:00
Shyam Jeedigunta
05fcefc0df
Make log-dump use 'gcloud ssh' for GKE also
2017-09-13 00:14:57 +02:00
Shyam Jeedigunta
c483c13aee
Correct logdump logic for kubemark master
2017-09-04 12:59:36 +02:00
Shyam Jeedigunta
a31703631f
Make logdump work for GKE with 'use_custom_instance_list' defined
2017-09-02 00:29:16 +02:00
Shyam Jeedigunta
aac1837218
Make logdump for kubemark logs independent of KUBERNETES_PROVIDER
2017-09-01 23:56:00 +02:00
Kubernetes Submit Queue
f2335d33d6
Merge pull request #50713 from MrHohn/dump-master-log-fix
...
Automatic merge from submit-queue (batch tested with PRs 50713, 47660, 51198, 51159, 51195)
Dump installation and configuration logs for master
**What this PR does / why we need it**:
We are dumping out empty configuration and installation logs on master, see `kube-node-configuration.log` and `kube-node-installation.log` on http://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce/12818/artifacts/bootstrap-e2e-master/ .
I guess it is just because [we name the services on master differently](https://github.com/kubernetes/kubernetes/blob/v1.7.3/cluster/gce/gci/master.yaml#L4-L40 )?
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #NONE
**Special notes for your reviewer**:
**Release note**:
```release-note
NONE
```
2017-08-24 11:17:01 -07:00
Shyam Jeedigunta
d2b6705dc8
Add some debug statements to logdump script
2017-08-23 11:51:58 +02:00
Zihong Zheng
7654e6a9d6
Dump installation and configuration logs for master
2017-08-15 13:50:02 -07:00
Shyam Jeedigunta
7456716120
Add debug logs to log-dump
2017-08-08 21:43:09 +02:00
Shyam Jeedigunta
73b419447f
Don't stop log-dumping if logexporter fails
2017-08-01 17:39:50 +02:00
Shyam Jeedigunta
80084f0621
Reduce kubectl calls from O(#nodes) to O(1) in cluster logdump
2017-07-31 13:20:53 +02:00
Shyam Jeedigunta
6c8ae3d5d7
Fix bug and add log statements to log-dump script
2017-07-28 22:33:30 +02:00
Shyam Jeedigunta
3ffc9ca34b
Fix log-dump script wrt logexporter
2017-07-27 00:09:59 +02:00
Shyam Jeedigunta
bf33e2ac7e
Fix bug in cluster/log-dump and add OWNERS file
2017-07-25 16:11:24 +02:00
Shyam Jeedigunta
ba7167963d
Fix bug with sed in log-dump script
2017-07-20 14:34:18 +02:00
Kubernetes Submit Queue
6af05149aa
Merge pull request #49058 from shyamjvs/logexporter-support
...
Automatic merge from submit-queue
Pass logexporter config through e2e framework
Ref https://github.com/kubernetes/kubernetes/issues/48513
/cc @wojtek-t @fejta
2017-07-19 09:57:47 -07:00
Shyam Jeedigunta
5cdedd22cf
Pass logexporter config through e2e framework
2017-07-18 23:28:06 +02:00
Shyam Jeedigunta
de09f8e569
Fix if condition in cluster/log-dump/log-dump.sh
2017-07-17 20:21:43 +02:00
Shyam Jeedigunta
5f8cb3d9ff
Enable logexporter mechanism to dump logs from k8s nodes to GCS directly
2017-07-12 14:39:49 +02:00
