Hello @ipxe-devel ,
Please pardon the confusion should we have given the wrong impression. We do
not expect anyone, not the IPXE maintainer(s) nor anyone else, to fix an issue
with IPXE that is impacting us and other IPXE users. I am very sorry should I
have given the impression that we expect others to fix issues we're impacted
from. We readily invest the time and effort to fix it ourselves.
We are relying on IPXE in a 3rd party environment - we provision kubernetes
clusters with a container OS in datacenters of public IaaS providers. IPXE is
supplied by our IaaS provider in their datacenters to download, install, and
boot custom OSes - in our case, Flatcar Linux. The OCSP bug in IPXE blocks us
from reliably using HTTPS to pull those OS images at provisioning time, so we
root caused and fixed this bug. The IaaS provider's datacenter operators rely
on upstream IPXE, so we are very interested in getting our fix upstreamed, and
we will eagerly implement any change proposed by IPXE upstream. Please verify
from the change history of this pull request that we will immediately jump into
action as soon as we get feedback.
I am very sorry should I have given the impression to expect upstream (or
others) to fix this issue. Let me state very clearly that *we* are willing to
invest into this fix until it is ready for ingestion. Please help us to
mitigate the pain this issue is inflicting on us and on other IPXE users.
Please provide feedback on the PR and help us to get it right for upstreaming.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/90#issuecomment-466669283
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
