Request access for kubespray #77
Comments
|
+1
…--
Dan Kohn <dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
On Sun, Aug 5, 2018 at 6:23 AM, Rong Zhang ***@***.***> wrote:
If you are interested in filing a request for access to the CNCF CIL,
please fill out the details below.
If you are just filing an issue, ignore/delete those fields and file your
issue.
First Name
River
Last Name
Zhang
Email
***@***.***
Company/Organization
Alauda
Job Title
Software Engineer
Project Title
Kubespray
Briefly describe the project
Kubespray (formerly known as Kargo), a subproject of Kubernetes, is a tool
for easily deploying production-ready clusters. It offers lots of options,
including high availability, and support for multiple platforms.
http://kubespray.io/
Which members of the CNCF community and/or end-users would benefit from
your work?
Kubespray and Kubernetes users
Is the code that you’re going to run 100% open source? If so, what is the
URL or URLs where it is located?
yes 100% open source.
https://github.com/kubernetes-incubator/kubespray
What kind of machines and how many do you expect to use (see:
https://www.packet.net/bare-metal/)?
t1.small.x86 -1
x1.small.x86 -4
What OS and networking are you planning to use (see:
https://help.packet.net/technical/infrastructure/
supported-operating-systems)?
Debian 8
CentOS/RHEL 7
OpenSuse 14.03
Ubuntu 16.04 LTS
Container Linux by CoreOS
Fedora/CentOS Atomic
Please state your contributions to the open source community and any other
relevant initiatives
- Switch to kubeadm deployment as the default method.
- Support more Provisioning and cloud providers(GCE, AWS, Openstack,
Digital Ocean, Azure,vSphere).
- Kubespray API
- Perform all actions through an API.
- Store inventories / configurations of mulltiple clusters .
- make sure that state of cluster is completely saved in no more
than one config file beyond hosts inventory
How will this testing advance cloud native computing (specifically
containerization, orchestration, microservices or some combination).
Kubespray is a Kubernetes incubator project that can be cluster created,
configured and managed .
It provides optional, additive functionality on top of core Kubernetes.
Any other relevant details we should know about while preparing the
infrastructure?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#77>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC8MBgR5GbTLJVTVcwB71aWfEyIkH3Vpks5uNse-gaJpZM4VvUnn>
.
|
|
@riverzhang, I have sent you an invitation email from Packet. Please let us know if you have any questions! |
|
Thanks a lot @dankohn @taylorwaggoner |
|
@taylorwaggoner how do we go about adding a couple of |
|
Hi @Miouge1 - EWR1 is a good place to deploy |
|
@Miouge1 - Here's a current look at your inventory on this project: This is quite a few more machines than was originally described - can you take a look |
|
Thank you for catching this @vielmetti ! The I think we can use the TerminationTime API option to set the max lifetime of the instances. I'm creating a GitHub issue to track this with more details: kubernetes-sigs/kubespray#7501
|
|
Thanks @Miouge1 ! All set for now here, I'll close this and watch the issue upstream. |
|
Upstream issue is equinix/docker-machine-driver-metal#59 to add a TTL parameter so that machines can be created with short expected lifetimes. |
|
Hello @riverzhang and @Miouge1 - The project "kubespray" currently has one host deployed to our If you could redeploy that system to a different data center that would be appreciated - I can help with specific locations if that's useful. It's likely that the nearest Asia data center with availability would be in Tokyo. |
|
@vielmetti I will start the migration soon. Thanks! |
|
Checking if there are any updates on this issue |
|
Remember when I said that Tokyo would be a good place to deploy a server? It was, for about 10 months. Now we need that server back to fulfill a contract. I'll share guidance on alternatives - if you can do a migration of that system promptly once I find you a suitable alternative location I would appreciate that greatly. Also and separately, the rest of the kubespray infra is deployed in our legacy (Packet) AMS1 data center, which is also being slowly but surely turned down as well in favor of new IBX (Equinix) data centers. After the Tokyo system is moved, let's plan a time to sync up and discuss plans to rehome everything else, identify which machines would be good to use etc. |
vielmetti
added
IBX Migration
|
@vielmetti thank you for the info. We are talking about server ID a95d5686-48d7-41c6-b78e-2a67fe71b063 right? I did not know about this server. The UI says "created by @riverzhang", it has some pods on it "karmada-runner" and some kubevirt: [root@kube-node2 ~]# kubectl get pods
NAME READY STATUS RESTARTS AGE
karmada-runner-j5gg8-575pj 2/2 Running 0 66d@riverzhang can you explain and could you cleanup or migrate as requested? |
|
This looks like Karmada https://github.com/karmada-io/karmada - it is a CNCF Sandbox project. I don't know much more than what it says about itself: "Karmada (Kubernetes Armada) is a Kubernetes management system that enables you to run your cloud-native applications across multiple Kubernetes clusters and clouds, with no changes to your applications. By speaking Kubernetes-native APIs and providing advanced scheduling capabilities, Karmada enables truly open, multi-cloud Kubernetes." |
|
Hello folks! We recently hit an issue with the two nodes kubernetes cluster set up on equinix metal which we use for the kubespray CI. The situation the cluster is in right now is not easily recoverable (see kubernetes-sigs/kubespray#8736) and we would like to ask permission to spin up a new cluster and move our CI over to the new one. This would require us to run the two setups side by side for a few days (2 weeks maybe) until we manage to get everything back up. |
|
Side by side setup is fine to make a transition. Please use gen3 instances (e.g. c3.small) instead of gen1 or gen2 (e.g. t1.small) for the new cluster, as mentioned above @cristicalin we are migrating away from our legacy data centers. |
|
Thanks @Miouge1 . @riverzhang - I don't know your working hours, and I am hopeful that we can get this promptly resolved. |
|
The CI and server reclamation issues have been resolved, thanks @mattymo for sorting this out. |
@vielmetti Do a demo in the karmada community, borrowing the service of kubespray.I'm sorry I didn't delete it in time. |
|
@riverzhang thank you for the info. Maybe a separate account for Karmada or for community events would be suitable? |
|
Reopening for more data center migration issues. As I mentioned back in April:
The time has come to do this migration, as our AMS1 center is closing. We have an equivalent alternative in our AM (Amsterdam) metro. There are three systems to be migrated (a Kubernetes cluster and a Docker machine runner). I see that the vast bulk of the on-demand testing is happening in our DA metro, so if you want to put the cluster there that's fine too. |
|
The migration step described in #77 (comment) has completed, closing this issue again. |
and others
If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.
If you are just filing an issue, ignore/delete those fields and file your issue.
First Name
River
Last Name
Zhang
Email
rongzhang@alauda.io
Company/Organization
Alauda
Job Title
Software Engineer
Project Title
Kubespray
Briefly describe the project
Kubespray (formerly known as Kargo), a subproject of Kubernetes, is a tool for easily deploying production-ready clusters. It offers lots of options, including high availability, and support for multiple platforms.
http://kubespray.io/
Which members of the CNCF community and/or end-users would benefit from your work?
Kubespray and Kubernetes users
Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?
yes 100% open source.
https://github.com/kubernetes-incubator/kubespray
What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?
t1.small.x86 -1
x1.small.x86 -4
What OS and networking are you planning to use (see: https://help.packet.net/technical/infrastructure/supported-operating-systems)?
Debian 8
CentOS/RHEL 7
OpenSuse 14.03
Ubuntu 16.04 LTS
Container Linux by CoreOS
Fedora/CentOS Atomic
Please state your contributions to the open source community and any other relevant initiatives
How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).
Kubespray is a Kubernetes incubator project that can be cluster created, configured and managed .
It provides optional, additive functionality on top of core Kubernetes.
Any other relevant details we should know about while preparing the infrastructure?
The text was updated successfully, but these errors were encountered: