Bug 1313414

Summary:	[DOCS] use 'atomic.io' as the base for the etcd config key when configuring flannel
Product:	Red Hat Enterprise Linux 7	Reporter:	Micah Abbott <miabbott>
Component:	doc-RHEL-Atomic	Assignee:	Chris Negus <cnegus>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vikram Goyal <vigoyal>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	7.2	CC:	cnegus, dornelas, yruseva, zdover
Target Milestone:	rc	Keywords:	Documentation, Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-15 03:36:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Micah Abbott 2016-03-01 15:05:25 UTC

Description of problem:

In the documentation for setting up a Kubernetes cluster [1], the configuration of flannel instructs the user to use an etcd config key of '/coreos.com/network'.  However, the flannel package is shipped with a default value of '/atomic.io/network'.  I think it would be preferable to use this default value in place of the 'coreos.com' value.

[1] https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#creating_a_kubernetes_cluster_to_run_docker_formatted_container_images


In section 3.5 "Setting up Kubernetes on the Master", the following commands/instructions should be changed:


# etcdctl set coreos.com/network/config < flannel-config.json

...should be changed to...

# etcdctl set /atomic.io/network/config < flannel-config.json


# etcdctl get coreos.com/network/config

...should be changed to...

# etcdctl get /atomic.io/network/config


The config file '/etc/sysconfig/flanneld' should have the following content:

FLANNEL_ETCD="http://master.example.com:2379"
FLANNEL_ETCD_KEY="/atomic.io/network"

Comment 2 Micah Abbott 2016-03-01 15:31:35 UTC

The same change will need to be made in section 3.6 "Setting up Kubernetes on the Nodes", Step 5.

Comment 3 Micah Abbott 2016-03-24 14:25:29 UTC

This is still an issue in the latest version of the docs:

https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#setting_up_kubernetes_on_the_master

Comment 4 Chris Negus 2016-09-19 18:07:18 UTC

I'll fix this for RHEL/Atomic 7.3.

Comment 5 Chris Negus 2017-03-13 20:04:46 UTC

The chapter identified here was corrected to use "atomic.io" as the base for the etcd configuration information. However, the chapter has since been dropped, because we no long support manual configuration of multi-node Kubernetes. I checked the other documentation in this area and we do properly identify "atomic.io" as the configuration base in our flannel documentation[1]. I think we can close this bug.

[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/#configuring_flannel

Comment 6 Vikram Goyal 2017-03-15 03:36:49 UTC

Thanks Chris. I will close this bug as CURRENTRELEASE based on your previous comment.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/#configuring_flannel

If there are any other issues, please open a new bug.