Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

var/log/containers symlink fluentd

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.2+coreos.0", GitCommit:"52a0d5141b1c1e7449189bb0be3374d610eb98e0", GitTreeState:"clean", BuildDate:"2016-07-19T17:45:13Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration:

aws

OS (e.g. from /etc/os-release):

NAME=CoreOS

ID=coreos

VERSION=1068.9.0

VERSION_ID=1068.9.0

BUILD_ID=2016-08-05-0455

PRETTY_NAME="CoreOS 1068.9.0 (MoreOS)"

ANSI_COLOR="1;32"

HOME_URL="https://coreos.com/"

BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

Kernel (e.g. uname -a):

Install tools:

kube-aws CLI tool

Others:

What happened:

looking at the fluentd-elasticsearch configuration in td-agent.conf, it says that the kubelet creates symlinks that capture the pod name, namespace, container name & Docker container ID to the docker logs for pods in the /var/log/containers directory on the host.

Unfortunately it looks like the /var/log/containers directory on our node hosts have been symlinked to the wrong place

it points to

var/log/containers -> /mnt/ephemeral/docker/containers

when i think it should point to /var/lib/docker/containers/

We are running in aws and using the kube-aws CLI tool

CoreOS 1068.8.0
Kubernetes v1.3.2

Is this a possible bug ?

What you expected to happen:

that the kubelet create symlinks correctly, i.e /var/log/containers is linked to the logs in /var/lib/docker/containers

How to reproduce it (as minimally and precisely as possible):

mount a volume on a pod e.g

volumeMounts:

- mountPath: /var/log

name: varlog

hostPath:

path: /var/log

name: varlog

Anything else do we need to know:

Nope

Issue 2:
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): ScheduledJobs API

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

Kubernetes version (use kubectl version): 1.4.1-beta.0.18

Environment:

Cloud provider or hardware configuration: minikube 0.12.0

OS (e.g. from /etc/os-release): Mac OS Sierra

What happened:

I am trying to create a scheduled job using the API (via kubectl proxy):

curl -X POST http://localhost:8001/apis/batch/v2alpha1/scheduledjobs -d @testscheduledjob.yaml -H 'Content-type:application/yaml'

Contents of testscheduledjob.yaml:

apiVersion: batch/v2alpha1
kind: ScheduledJob
metadata:
name: hello
spec:
schedule: 0/1 * * * ?
jobTemplate:
spec:
template:
spec:
containers:
- name: hello
image: busybox
args:
- /bin/sh
- -c
- date; echo Hello from the Kubernetes cluster
restartPolicy: OnFailure

I get this error:

{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "the server does not allow this method on the requested resource",
"reason": "MethodNotAllowed",
"details": {},
"code": 405
}

Is there a way to create a scheduled job other than using kubectl at the moment?

Anything else do we need to know:

Trying to create a scheduledjob from inside a container