-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
baremetal: Add coredns, mdns-publisher, haproxy, keepalived static pods #795
baremetal: Add coredns, mdns-publisher, haproxy, keepalived static pods #795
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First, this duplicates/overlaps #740 right?
The .gitkeep
files shouldn't be necessary anymore.
templates/master/00-master/baremetal/files/baremetal-chrony.yaml
Outdated
Show resolved
Hide resolved
templates/master/00-master/baremetal/files/baremetal-clusterinfo.yaml
Outdated
Show resolved
Hide resolved
templates/master/00-master/baremetal/files/baremetal-fletcher8.yaml
Outdated
Show resolved
Hide resolved
templates/master/00-master/baremetal/files/baremetal-get-vip-subnet-cidr.yaml
Outdated
Show resolved
Hide resolved
There is some little overlap, but does not directly duplicate. If you have a suggestion for de-duping between just two platforms, that would be helpful. I'll remove the .gitkeep files. |
e1fc4a0
to
d1947b8
Compare
79a77c0
to
71395f2
Compare
Sorry about the delay on this...there's a lot going on and we may need periodic pings if PRs are important/ready. I feel like this would probably be best as a separate git repository, with the contents built into one or more container images. The relevant code in the MCO would boil down to injecting the static pod entries, much like is done for etcd. Among other things, that would avoid the awkward shell-script-in-yaml-in-yaml and more generally allow your team to easily iterate on the content without blocking on us here. |
We are working on the amount of shell-scripty things. Is there an existing component with such a repo that I can look at? |
Since the runway is relatively short here for 4.2, we discussed landing this roughly as is and iterating from there. One argument to having this be a separate operator/controller was that the MCO's role here should be more around "infrastructure" rather than platform-specific code, but on the other hand in practice actually the MCO codebase has a lot of convenient parts for this (templating MachineConfig files based on data from the cluster config), plus its already extant support for platform conditionals for MachineConfig, etc. Another aspect is that these templates also need to run at install time for the masters, and introducing a new operator/controller rendering MachineConfigs would require changes to the installer's |
e4c2117
to
25393f3
Compare
71e06a3
to
48de99f
Compare
2161280
to
2755d5b
Compare
/retest |
34c3c06
to
341a752
Compare
…g images This patch adds the images so they can be referenced from templates.
bf809d6
to
07c4311
Compare
@runcom Review please. |
/hold cancel |
Adds pods to master and worker nodes as appropriate Updates haproxy container to use openshift/router-haproxy image instead of docker.io/library/haproxy Also adds liveness tests for the coredns,mdns-publisher, haproxy and keepalived static pods, changes worker node /etc/resolv.conf to point to node's IP instead of 127.0.0.1 and fix the bug generating haproxy cfg file Due to the fact that both use the same image, there was a bit of confusion here. We want keepalived to track OCP Router 1936 and we want API LB Haproxy pod to have health checked at 50936, which is where we configure haproxy to expose health at. Depends-On: openshift#943 Depends-On: openshift#984
an exception has been granted for this so |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bcrochet, celebdor, cgwalters, runcom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
In order for the baremetal infra services to use the images from the release, we need to look up the correct image during bootstrap and pass that in to the MCO. The new image parameters were added to MCO in openshift/machine-config-operator#795 Part of the changes for openshift#2067
Adds pods to master and worker nodes as appropriate for baremetal deployment.
Requires: #943