Sorry for the newbie questions but...
Snapshot20180829 is out but it looks to be almost exactly the same as
snapshot Snapshot20180820. Is this correct?
Jason
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org
Hello,
I'm happy to announce that the Kubic Project status update meetings will happen
every Tuesday at 17:00 CEST.
The meeting will happen at chat.freenode.net, on #kubic IRC channel.
Cheers,
Rafa.
Hello,
I'd like to start the discussion on when to set the weekly meetings for the
Kubic progress and for syncing efforts and goals.
* What's the expectation on the medium of the meeting?
* IRC
* Voice
If we choose IRC, these meetings can be saved and we can keep history over them;
if we choose Voice, it would be great to take minutes notes and also keep them as
history.
As for the day, I don't have a very tight schedule so I think others can propose.
--
Cheers,
Rafa.
Hi All,
As the subject says, there are now some highly experimental disk
images available for Kubic
They're built in OBS in the devel:kubic:images:experimental project
https://build.opensuse.org/project/show/devel:kubic:images:experimental
Please read and understand the description of that repository before
diving in and playing with the images. The main reason for these
warnings are as follows
- The images are 100% not tested
- The images are not released as part of the Tumbleweed release
process, so there is always the risk of a mismatch between the images
and 'official' Tumbleweed/Kubic
- The images are known to have some discrepancies from official Kubic
- for example the partitioning is known to be different but cannot be
corrected due to limitations of our image building tooling.
I hope they're helpful but care should be made to avoid us running
around in circles hunting bugs which only exist in these images. So if
you find a bug with these images, please try and reproduce it with the
official Kubic ISO media.
The image names relate to both the system role and container runtime
in use - MicroOS images are designed to be standalone container hosts,
kubeadm images should be usable to make kubeadm clusters using the
guide on kubic.opensuse.org. Both cri-o and docker flavours are
available.
There are a number of build targets for the Project, and they require
some additional explanation
images - https://download.opensuse.org/repositories/devel:/kubic:/images:/experiment…
These are built against official, released, Tumbleweed snapshots. At
time of writing they are 100% known to be BROKEN because Tumbleweed
doesn't contain the changes needed to make them work right. For
example, the images called 'cri-o' contain docker ;)
images_ARM - https://download.opensuse.org/repositories/devel:/kubic:/images:/experiment…
Same as above, just for ARM
images_devel_kubic -
https://download.opensuse.org/repositories/devel:/kubic:/images:/experiment…
These are built against the untested, unreleased devel:kubic Project.
At time of writing these are the best images because devel:kubic
contains everything needed by the images. They'll be most likely to
break going forward, but for now they're the best images to play with
until the ones in Images get working.
images_devel_kubic_ARM -
https://download.opensuse.org/repositories/devel:/kubic:/images:/experiment…
Same as above, just for ARM.
Enjoy, and happy hacking
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org
Hello all,
I have created some cards in a new column "To be refined". The idea is to
settle some requirements we need in order to be feature-complete as CaaS
Platform is today, but keeping in mind the most important tasks that need
to be done in order to validate the new architecture, as well as identify
as soon as possible hazards and uncertainties that we might hit at some
point.
Please, feel free to modify, comment or add new cards to that column. I'd
like to keep this column until next Friday -- after that we can move all
cards to the "To Do" column and delete this column.
I've taken the "Init container" card and started to work on it (so it's on
the "Doing" column), but feel free to also comment on that one if needed.
In general, I added the "Platform" label to all these cards, which means
platform basic pieces to be feature-paired to some extent to CaaS Platform
but with the alternative architecture.
You can find also an "On Hold" label that I have used to mark tasks that
can wait a little before we have something that works and can build upon.
The board can be found at [1], as per Richard's ML opening email.
Cheers,
Rafa.
[1] https://trello.com/b/wjHyQDK6/kubic-project
Hi all,
As we are moving to cri-o by default, I've just sent the following
SR's to devel:kubic (and
devel:CaaSP:Head:ControllerNode in the case of docker-kubic)
cri-o 629274
kubernetes 629273
patterns-caasp 629272
docker-kubic 629275
TLDR; PLEASE DO NOT SUBMIT THE ABOVE SR's to Factory.
Feel free to review, comment, accept to devel:kubic, but do not to
Factory - I will take care of that.
Aleksa/anyone
I also have an open question - docker-kubic automatically resolves
these two issues with kubeadm:
[ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]:
/proc/sys/net/bridge/bridge-nf-call-
iptables does not exist
[ERROR FileContent--proc-sys-net-ipv4-ip_forward]:
/proc/sys/net/ipv4/ip_forward contents are not set
to 1
Now I've replaced it with CRI-O people need to "modprobe br_netfilter"
and "echo '1' >
/proc/sys/net/ipv4/ip_forward"
How does docker-kubic take care of that so we can consider a similar
solution over in crio kubic?
Long explanation below:
To explain why all of this has changed, I need to cover what they
collectively do (or should do - this all
worked on my machine in testing):
- Define crio as our default runtime for k8s, and now part of the
official 'container-runtime' pattern (which
also includes podman)
- Define docker as our alternative runtime, and now provided by the
official new 'alt-container-runtime'
pattern (named for both english 'alternative' and german 'alt')
- Makes kubernetes requires either runtime. Should be able to pick
what they like and we can easily make
images with either.
- Adds support to kubeadm to read a config file for easy CRI runtime
definition by users or by packages (patch
also submitted upstream)
- Adds a subpackage to both runtimes to provide the CRI config file
now used by kubeadm
These changes are dependant on the following changes to the product
configuration also
https://github.com/yast/skelcd-control-Kubic/pull/19/files
This installs both runtimes on MicroOS (for maximum exposure and
comfort for people who just want 'docker')
For kubeadm it will only install CRI-O by default
All of these changes need to be somewhat coordinated. The packages
need to land at the same time - and that
should be before/at the same time as the skelcd changes (which will be
going through the YaST CI)
And I do not want any of these changes to land before the already
submitted changes reach Factory
I want the world to enjoy nice shiny Kubic kubeadm image that works as
well as my current test system before I
risk breaking it with this plumbing
Therefore please, even if you accept the above SR's to devel:kubic,
make sure the "Forward to Factory" tickbox
is NOT selected. I'd like to decide when these changes go to Factory please
Thanks!
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org
Hi all,
While investigating the current master promotion issues with kubeadm i
noticed a few things
1) our /etc/kubernetes/* config files do not seem to reflect that
which is expected by k8s upstream
eg. no kubelet.env file
https://github.com/kubernetes/kubernetes/blob/master/build/rpms/kubelet.env
2) we are not using upstream kubeadms config file - eg.
https://github.com/kubernetes/kubernetes/blob/560e15fb9acee4b8391afbc21fc3a…
I've therefore created
https://build.opensuse.org/project/show/devel:kubic:vanilla
This is a temporary devel project which will create an alternate
kubernetes package with all of the /etc/kubernetes/* configurations
removed, and the upstream kubeadm config file present
It's not expected to work right away, hence keeping it separate from
the kubernetes package in devel:kubic
If this tidy up bears fruit, then devel:kubic:vanilla will die and
whatever we learn from this effort will be merged in devel:kubic
Anyone looking at getting kubeadm working is welcome to either
contribute to the 'tidyup and sync' efforts in devel:kubic:vanilla or,
if you think minor alterations are all that's needed, regular tweaks
to devel:kubic will still be welcome
Regards,
Rich
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org
I think it would be nice to schedule regular sync meetings between all
the people involved with the project.
Maybe we could hold them every two weeks?
Cheers
Flavio
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org
Hi All,
The Kubic Project, producing a Tumbleweed variant focused on container
technologies like Kubernetes, is changing it's focus to integrate more
closely with upstream tools like kubeadm
For more details please read the full announcement here:
https://kubic.opensuse.org/blog/2018-08-09-newdirection/
Please use this opportunity to join in and contribute to this new era
of the Kubic project.
And, as part of this effort, we've made a new
opensuse-kubic(a)opensuse.org mailinglist - please keep any discussion
to that mailinglist so we can keep this opensuse-factory@ list nice
and focused.
Regards,
The Kubic Team
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org
Welcome to the Kubic Mailinglist, where we're going to be talking
about Kubic without creating noise on opensuse-factory(a)opensuse.org
Like -factory, this is intended to be mostly a technical mailinglist
discussing everything we're working on for Kubic
The creation of this list is part of the fresh effort to refocus Kubic
more towards upstream Kubernetes and tools like kubeadm
Everyone can track everything we're doing on our new trello board -
https://trello.com/b/wjHyQDK6/kubic-project
And for those who don't like mailinglist, we're also going to be
reachable via the #kubic IRC channel on freenode
Have a lot of fun,
Richard
--
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org