Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Bump istio to 1.0.1+ #230
There is a performance issue in 1.0.0 that is fixed in subsequent versions istio/istio#6962. I would have submitted a PR but the instructions allowing reuse of the downloaded resources for building the snap don't work, meaning I would have to find a way to clean and rebuild downloading everything again (I have only a slow wireless connection with a bandwidth cap) and snap is still very broken for rebuilding (see https://bugs.launchpad.net/snapcraft/+bug/1582469).
I already downloaded and set up a VM with 16.04 because trying to build on 18.04, even using cleanbuild, didn't work either (though admittedly I have lots of potentially conflicting stuff installed - docker, microk8s, then lxd...).
I tried everything I could think of but it looks like I might have to dive into the code of snapcraft in order to build microk8s. Not a wonderful experience for contributors!
Edit: I ended up doing a full clean and managed to produce a snap. Unfortunately, it looks like something else happened and the package that was produced was missing libreadline.so.6, so several of the services refused to start.
Thank you for opening this issue. Apologies for the poor experience you had in building the snap with pre-fetched binaries. The issue is addressed in this PR: #237 Most of our builds are now done through travis and launchpad builders so we haven't tested this approach for a long time. Regardless, it should have worked.
I have never seen this "missing libreadline.so.6" error, could you share the full build process (steps and output) you are following?
We appreciate your time and effort to improve MicroK8s and we are here to assist in any way we can.
@AntonOfTheWoods you must have already seen that the istio update is a single line patch https://github.com/ubuntu/microk8s/blob/master/build-scripts/prepare-env.sh#L16
Ok, so I did a completely fresh pull of microk8s and rebuilt with
Looks very much like it is expecting a shared lib to be present somewhere and it's not. It does appear to be present in the core at
I had a completely different problem on the Ubuntu 16.04 VM - it was refusing to
I am not sure what use I can be without really deeply diving into how snap and microk8s works. I'll confess that I've already manually installed istio (+ manually activated RBAC) and it seems to be working well... so my itch-scratching level is pretty low on this one now :-). If there is anything particular I can do let me know, if I can help with low time investment I'm definitely keen!
@AntonOfTheWoods I could not reproduce the missing libreadline error. I believe the problem is with snapcraft build process that does not pull the expected dependencies in the snap. The snapcraft team is aware of such issues and therefore are pushing towards builds inside lxc containers. This should be transparent to you.
Could you try this:
On the taint errors, could you see if the node is under disk or memory pressure? Try:
What exactly did you have to do to enable RBAC, you mentioned some manual steps, could you share those?
Your feedback is very important to us. Keep opening issues for any big or small thing you find. We appreciate your time and effort you spent in improving MicroK8s. Thank you.
Sorry, I tried a couple more times but really my bandwidth is precious and my connection flakey - I am in China and some stuff (notably everything @google) simply won't work if it doesn't go over a VPN, I have only an (often slow) 4G connection and a flakey wifi router (an old Android phone...). I got to the download of the kube elements but the VPN connection got lost and it wouldn't come back, meaning starting everything again in a new lxd container...
Well spotted :-). Sorry, I'm still a Kube-n00b and hadn't noticed that the VM was almost out of disk space. Removing failed build attempts solved the issue for Ubuntu 16.04.
I just followed #84 (comment). I'll confess I didn't check things like the dashboard afterwards (#220 would suggest it gets broken) but I was able to follow the instructions to install helm with RBAC (https://github.com/helm/helm/blob/master/docs/rbac.md) and then install istio with that helm (https://istio.io/docs/setup/kubernetes/helm-install/). I was then able to get to some pods I had spun up via an istio gateway, so for me that was sufficient to think "it works". There may well be issues down the road.
If my connection weren't so bad I'd love to do more! Thanks for your great support.