Added proposal for K8s on LinuxOne #50
Conversation
Signed-off-by: Rajula Vineet Reddy <rajula96reddy@gmail.com>
| @@ -0,0 +1,113 @@ | |||
| * Name of project (must be unique within OMP) | |||
|
|
|||
| Kubernetes on LinuxOne | |||
There was a problem hiding this comment.
We should probably drop the 'LinuxOne' term and use 's390x' instead to avoid product names.
There was a problem hiding this comment.
Kubernetes already builds on s390x. What would the real purpose of this project be?
There was a problem hiding this comment.
We should probably drop the 'LinuxOne' term and use 's390x' instead to avoid product names.
Sure. I thought the same. I will make the changes.
Kubernetes already builds on s390x. What would the real purpose of this project be?
Only the Kubernetes binaries are supported for s390x. But the network plugins, e2e tests and other plugins are not supported as of now. Check kubernetes/examples#318 and https://k8s-testgrid.appspot.com/sig-node-ppc64le#conformance. This requires building and maintaining different Dockerfiles.
There was a problem hiding this comment.
@markkp Does @rajula96reddy's response answer your question?
There was a problem hiding this comment.
We should probably drop the 'LinuxOne' term and use 's390x' instead to avoid product names.
zLinux is another term used in the industry that is not a product but a reference to Linux on Z hardware
There was a problem hiding this comment.
Many of our projects have gone the route of a codename that alludes to the focus of the project ( for example, Feilong for the the previous z/VM Cloud Connector work ). That might be another good option - which at the same time opens up the possibility of a cool looking logo LOL.
We can work more on the project name during incubation if the TSC is fine with that.
There was a problem hiding this comment.
@markkp Does @rajula96reddy's response answer your question?
Yes.
|
Seeing where this stands - working on the agenda for the September meeting and would like to get this added if y'all think you will be ready. |
|
Katharos … means pure in Greek … could allude to a port.
Matt Hogstrom
matt@hogstrom.org
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook <https://facebook.com/matt.hogstrom> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://twitter.com/hogstrom>
“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
… On Sep 2, 2019, at 7:56 AM, John Mertic ***@***.***> wrote:
@jmertic commented on this pull request.
In projects/proposals/K8s on LinuxOne.md <#50 (comment)>:
> @@ -0,0 +1,113 @@
+* Name of project (must be unique within OMP)
+
+Kubernetes on LinuxOne
Many of our projects have gone the route of a codename that alludes to the focus of the project ( for example, Feilong for the the previous z/VM Cloud Connector work ). That might be another good option - which at the same time opens up the possibility of a cool looking logo LOL.
We can work more on the project name during incubation if the TSC is fine with that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#50>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWFPJ2HI5H44E2PR5VWQVTQHT5NDANCNFSM4H7IBH2Q>.
|
|
The installation of a basic kubernetes cluster became a lot easier in v1.12 or v1.13 using kubeadm. The initial intent of this project was to provide how-tos because k8s was difficult to install. I think how-tos are still valuable for each supported distro. I see this project addressing the more complex aspects of k8s that might not work as well on s390x. Things like e2e, popular network (CNI) and storage (CSI) interfaces that might not work on s390x. I agree this is ready to be discussed by the TSC. |
|
Thanks for the feedback here @mfriesenegger ! Would you see the code created flow into upstream Kubernetes, or is this something that would sit outside of Kubernetes upstream? |
No description provided.