How to list CoreOS updates ?

[Parag Gupta]

Hello, can anyone tell me how can I see updates downloaded in partition B(inactive)?

Please share the command to the list of downloaded updates

[Rob Szumski]

Only one update is downloaded at a time to the inactive partition. You can see that with the journal: https://coreos.com/os/docs/latest/switching-channels.html#debugging

On Wed, Oct 23, 2019 at 6:45 AM Parag Gupta <paraggu...@gmail.com> wrote:

Hello, can anyone tell me how can I see updates downloaded in partition B(inactive)?

Please share the command to the list of downloaded updates

--
You received this message because you are subscribed to the Google Groups "CoreOS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/coreos-dev/db30d74d-4fbb-40ae-80a3-fe2847f1f62e%40googlegroups.com.

[Neil Mayhew]

There's a good description of how the system switches between root partitions here, including information on how to see which one is going to boot next.

[Parag Gupta]

Thankd Rob for your reply . i got your point so only 1 package will get downloaded which is  coreos update (this might incluyde update for different services like etcd/fleet or any other package but all bundled into 1 coreos update). it will bump coreos version to the latest one (as per selected channel). I can see if this is available or not . am i right ?

On Wednesday, 23 October 2019 19:00:28 UTC+5:30, Rob Szumski wrote:

Only one update is downloaded at a time to the inactive partition. You can see that with the journal: https://coreos.com/os/docs/latest/switching-channels.html#debugging

On Wed, Oct 23, 2019 at 6:45 AM Parag Gupta <paraggu...@gmail.com> wrote:

Hello, can anyone tell me how can I see updates downloaded in partition B(inactive)?

Please share the command to the list of downloaded updates

--
You received this message because you are subscribed to the Google Groups "CoreOS Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to coreo...@googlegroups.com.

[Nick Stielau]

Hey Parag, 

Since you mentioned Fleet, I wanted to make sure you knew it was deprecated in favor of kubernetes: https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html

And while I'm mentioning deprecations, I wanted to make sure you knew that Container Linux will sunset next year, and Fedora CoreOS will be the new general-purpose immutable host we are investing in: https://docs.fedoraproject.org/en-US/fedora-coreos/faq/

To unsubscribe from this group and stop receiving emails from it, send an email to coreos-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/coreos-dev/53be41e9-d58c-4e02-8472-937eccddeea7%40googlegroups.com.

--

-----

Nick Stielau

He - Him - His

SFO, OpenShift

[Parag Gupta]

Hello Nick, i am aware about this that container Linux is going to decomission. i have one question from you that i learned that kubernetes uses etcd . So if i launch coreOS cluster using kubernetes so will it use coreOS etcd or its own etcd ? (this might be a silly question but i am confused about this) 

On Thursday, October 24, 2019 at 9:12:02 PM UTC+5:30, nstielau wrote:

Hey Parag, 

Since you mentioned Fleet, I wanted to make sure you knew it was deprecated in favor of kubernetes: https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html

And while I'm mentioning deprecations, I wanted to make sure you knew that Container Linux will sunset next year, and Fedora CoreOS will be the new general-purpose immutable host we are investing in: https://docs.fedoraproject.org/en-US/fedora-coreos/faq/

On Thu, Oct 24, 2019 at 5:51 AM Parag Gupta <paraggu...@gmail.com> wrote:

Thankd Rob for your reply . i got your point so only 1 package will get downloaded which is  coreos update (this might incluyde update for different services like etcd/fleet or any other package but all bundled into 1 coreos update). it will bump coreos version to the latest one (as per selected channel). I can see if this is available or not . am i right ?

On Wednesday, 23 October 2019 19:00:28 UTC+5:30, Rob Szumski wrote:

Only one update is downloaded at a time to the inactive partition. You can see that with the journal: https://coreos.com/os/docs/latest/switching-channels.html#debugging

On Wed, Oct 23, 2019 at 6:45 AM Parag Gupta <paraggu...@gmail.com> wrote:

Hello, can anyone tell me how can I see updates downloaded in partition B(inactive)?

Please share the command to the list of downloaded updates

--
You received this message because you are subscribed to the Google Groups "CoreOS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/coreos-dev/db30d74d-4fbb-40ae-80a3-fe2847f1f62e%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "CoreOS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/coreos-dev/53be41e9-d58c-4e02-8472-937eccddeea7%40googlegroups.com.

[Nick Stielau]

On Thu, Oct 24, 2019 at 10:43 PM Parag Gupta <paraggu...@gmail.com> wrote:

Hello Nick, i am aware about this that container Linux is going to decomission. i have one question from you that i learned that kubernetes uses etcd . So if i launch coreOS cluster using kubernetes so will it use coreOS etcd or its own etcd ? (this might be a silly question but i am confused about this) 

Kubernetes needs to connect to an etcd cluster.  Typically, an installer for kubernetes (like Red Hat's OpenShift Installer) will co-locate the etcd cluster on the Kubernetes master nodes, which also have the API servers that would be reading/writing to etcd.

I'm not sure exactly what you mean by "launch a coreOS cluster using kubernetes."  You could run your Kubernetes cluster on top of Container Linux nodes (as CoreOS company did with their Tectonic enterprise Kubernetes product).  You could also run an etcd cluster on Container Linux, and create a Kuberenetes cluster running on RHEL that connected to the etcd cluster running on etcd (not sure why you'd do that, just trying to express flexibility).

I think splitting out the host operating system, the etcd datastore, the kuberenetes api-server and your applications is a good idea when thinking about Kubernetes architecture.

Hope that helps!

-Nick

 

To unsubscribe from this group and stop receiving emails from it, send an email to coreos-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/coreos-dev/1b80eb41-e57a-4218-adbd-d3975f102326%40googlegroups.com.