-
Notifications
You must be signed in to change notification settings - Fork 30
cloud-config: deprecate etcd2 and etcd and create new docs #1877
Comments
cc @coreos/team-docs we should do this ASAP. |
Instead of coreos-cloudinit, we are going to show how this can be done via Container Linux Configs instead (coreos/container-linux-config-transpiler#37). |
as discussed, will wait for the etcd team to complete the new version of docs that they are working on. Then we would be able to provide proper links to the docs, along with stating etcd2 is depreciated. |
The etcd team has finished most of the documentation (if not all of it). We are really just waiting on the ct documentation @dgonyeo is working on. It should be ready by the end of the week. |
@dgonyeo ping us once you merge the changes! |
@crawford We need both cloud-config and ignition, because:
|
@radhikapc the ct docs were merged: coreos/container-linux-config-transpiler#37 I'm now working on changing all the docs in coreos/docs to use container linux configs: coreos/docs#1024 This change results in the docs for all the platforms I can update (as in, have ignition support) being switched over to etcd v3. It's not in the cloud-config docs like this issue wanted, but mentioning it here because it's very related. |
Thanx @dgonyeo. will look into this shortly. |
Hello everyone, \o/ I am interested in new documentation of etcd3 and the use of CT that is not very clear at the moment. I want to do a tutorial on using ignition 2.0, etcd3, TLS / SSL and firewall rules and provisioning with ansible + shell script on a solid CoreOS. In this link #1882 I approach some questions to start the tutorial with the use of etcd3 principally. I am eager for more explanatory documentation and examples. |
From my glance through the etcd docs, the following work for etcd3 on container linux: The following have CL specific bits that reference an old etcd (and a new one as well often):
(nit: https://coreos.com/etcd/docs/latest/upgrades/upgrade_3_0.html assumes The following do not use etcd3 in a way that would work on container linux (e.g. the etcd binary or otherwise have a broken reference):
The second section there are more egregious. @dgonyeo feel free to clarify or update the above list, I might be misunderstanding something. cc @gyuho since I think some of number-2 are related to your change in coreos/docs#1016 Removed from the CL project since this is not coupled to a release |
As per the discussion with @heyitsanthony we need new set of docs specific to Container Linux for the following: https://coreos.com/etcd/docs/latest/op-guide/clustering.html |
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
/etcd/etcd-live*: deprecate etcd2 and etcd Ref: coreos/bugs#1877
@euank all the issues you have mentioned have been fixed and doc is merged, please go ahead and close this defect unless we have new set of docs to be fixed other than what we have mentioned here. |
related #1128 is closed. |
In a blog post a few weeks ago we announced deprecation of etcd2 and etcd in Container Linux. But, our docs haven't been updated. We need to do the following things:
Show people how to use etcd-member in the cloud-config docsIssue filed based on feedback from Twitter: https://twitter.com/spidler/status/844350222524448773
The text was updated successfully, but these errors were encountered: