Alex
Alex
Some folks seem to be upgrading there bastions to rhel9 and it is unclear if we need any changes to the setup bastion playbook in order to support rhel9.
We should research the feasibility of refactoring the du profile into separate ansible roles one for with pre cluster install tasks to facilitate adding du profile manifests prior to installing...
One of the desired features of Jetlag would be the ability to scale up a cluster after an initial cluster is installed. We need to research scale up methods for...
There should be a way to nat the ipv6 traffic through the bastion onto the public ipv4 network such that ipv6 clusters could be connected clusters. We need to research...
All guides should be written as if they are running from the bastion machine in an allocation. This will make all guides consistent, as well as remove the inconsistency of...
Developing changes for jetlag can be tough to ensure that we do not make a breaking change. Having a CI will help prevent an accidental breaking changes. We should have...
Instead of referring to standard (3 control-plane, X worker nodes) and compact clusters as "Bare Metal" we should rename the terminology to MNO or Multi-Node OpenShift. This makes it simpler...
It seems not actually in use, I am unsure of how we arrived at the conclusion it was to be added to the byol document.
We need to replace dnsmasq on the bastion with coredns to see if the ANY query issue occurs. It plagues ipv4 and ipv6 disconnected clusters during the post deploy phase...
It is not clear to me this is in use anymore and is a rather confusing var. We should seek to remove it to avoid confusion.