-
Notifications
You must be signed in to change notification settings - Fork 295
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
Masters and Workers can't pivot behind the proxy #19
Comments
I saw this during sshing into the server:
|
|
It seems as if the machine-config-daemon is an empty binary:
|
The service If I set the proxy manually in the systemd file for it, and restart the both services:
The downloads work until the master restarts. So in my opinion the proxy credentials should be rendered in the ignition files which are served from the bootstrap server to the masters and workers. |
Dupe of #14? |
@vrutkovs: |
Ah, I see now. Please rename to "Master can't pivot behind the proxy". OKD-specific |
A workaround I used to get the installation (OKD beta5) working behind a firewall is to execute the following in every master and worker on first boot:
|
Fix merged in 4.4.0-0.okd-2020-06-02-224917 (thanks @evertmulder!), also backported to fcos-4.5 branch |
Hi,
I try to install OKD4 on vSphere like this:
https://docs.openshift.com/container-platform/4.2/installing/installing_vsphere/installing-vsphere.html#installing-vsphere
For sure I had to change the version of the append-bootstrap.ign from 2.x.x to 3.0.0 to get it running on the bootstrap server.
I set the platform to 'none' because I create the ignition files and manually create the VMs in vSphere with them.
I'm behind a corporate proxy. Because of that I used the proxy settings in the install-config.yaml.
If I ssh into the bootstrap server the proxy env vars are set. The bootstrap server initialization runs successfully, it servers the ignition files for masters and workers on port 22623.
If I ssh into the master server, I see this in the journal:
This also doesn't work:
sudo podman run hello-world
It seems as if the proxy.sh is missing in /etc/profile.d on the master.
Greetings,
Josef
The text was updated successfully, but these errors were encountered: