-
Notifications
You must be signed in to change notification settings - Fork 672
Add weave-kube DaemonSet that can be used with k8s version v1.6 #2801
Conversation
I ran a test to check what happens if you load this file on k8s 1.5:
So we need to figure out how best to help our users. #2754, perhaps. |
@bboreham Totally known issue, this is what's hard with providing manifests; they often have to track the release branches of k8s In this case; Taints and Tolerations was alpha in v1.5; now beta. The same goes for RBAC, hence the above error. RBAC beta did obviously not exist in v1.5. We have to provide different manifests for v1.5 and v1.6 users somehow |
Comment copied from #2777: Note fluxcd/flux#400 (comment):
so I tried this, and it seemed to work at https://circleci.com/gh/weaveworks/weave/8146 (albeit the 'publish' phase failed on branch naming) |
- name: cni-conf | ||
mountPath: /host/etc | ||
- name: dbus | ||
mountPath: /host/var/lib/dbus |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
I'm seeing a couple of problems when I apply this to the latest beta of kubeadm/k8s.
It looks like there is an error about a missing env variable. Is this the env variable for the kubernetes service? |
"cni config uninitialized" suggests the Weave Net pods never got started, because they write out the config. Do you see anything in their logs? |
The weave pods were definitely up. I suggest you try the latest kubeadm to see if you can repo. |
The kubelet has some errors like this:
|
I managed to achieve error-message parity with you, @jbeda:
All of this derives from the kube-dns infrastructure container being dead:
It looks like kubelet is getting hung up on the repeated failure That environment variable used to be mandated by the CNI spec, but the spec was changed a couple of months back to allow it to be unset, and when I updated the Weave Net plugin to honour that change it all works. That update to the plugin is in #2850 but is not merged yet. |
d18e9cf
to
0f5ab09
Compare
@luxas I think I'm in parallel with you - see branch luxas-add-head-manifest I think the file should be named '1.6' rather than 'HEAD' |
serviceAccountName: weave-net | ||
securityContext: | ||
seLinuxOptions: | ||
type: spc_t |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
@bboreham @errordeveloper @lukemarsden
ref: #2777