mirror of https://github.com/k3s-io/kubernetes.git synced 2026-01-30 05:43:58 +00:00

Files

Javier Diaz-Montes 9743cda4a7 Adding Kubelet changes to enable SetHostnameAsFQDN feature

These changes allow to set FQDN as hostname of pods for pods
that set the new PodSpec field setHostnameAsFQDN to true. The PodSpec
new field was added in related PR.

This is PART2 (last) of the changes to enable KEP #1797 and addresses #91036

2020-06-14 21:26:27 -04:00

apparmor.go

…

BUILD

Adding Kubelet changes to enable SetHostnameAsFQDN feature

2020-06-14 21:26:27 -04:00

crictl.go

…

events.go

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00:00

framework.go

…

kubelet_perf.go

…

kubelet.go

Update .import-aliases for e2e test framework

2020-03-25 11:40:02 +08:00

mount_propagation.go

…

node_problem_detector.go

generated: run refactor

2020-02-07 18:16:47 -08:00

OWNERS

…

pod_gc.go

generated: run refactor

2020-02-08 12:30:21 -05:00

pod_hostnamefqdn.go

Adding Kubelet changes to enable SetHostnameAsFQDN feature

2020-06-14 21:26:27 -04:00

pods.go

e2e pods: add missing pod and node name in the formatted log line

2020-06-11 14:50:27 -05:00

pre_stop.go

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00:00

README.md

…

runtimeclass.go

test/e2e/framework : move AddOrUpdateTaintOnNode to subpackage node

2020-04-29 21:29:38 +08:00

security_context.go

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00:00

ssh.go

…

taints.go

test/e2e/framework : move AddOrUpdateTaintOnNode to subpackage node

2020-04-29 21:29:38 +08:00

ttlafterfinished.go

generated: run refactor

2020-02-08 12:30:21 -05:00

README.md

WARNING: Do not add tests in this directory

There are two types of end-to-end tests in Kubernetes:

Tests located in ${KUBE_ROOT}/test/e2e/common are shared by both Cluster and Node E2E test jobs. Tests in ${KUBE_ROOT}/test/e2e_node are exclusively owned by Node E2E. If you want to add a test, most likely than not, you want to add the test to one of the two directories mentioned above. If you are unsure, please check with the OWNER of the directory. This directory currently contains misplaced and legacy tests; they will be cleaned up in the future.