RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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"

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

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

I'll fix this for RHEL/Atomic 7.3.

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

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.