JakubLedworowski
JakubLedworowski
@steven-bellock yes, that approach works for me as long as the integrator has the option to use the transport layer methods directly (eg. libspdm_transport_mctp_encode_message) to avoid code duplication as it...
Hi, Is there any update on this issue? I have the same problems with k3s v1.28.7: operator-sdk version: "v1.33.0" kubernetes version: "1.27.0" go version: "go1.21.5" I'd appreciate any hints ;)
Hi, I actually managed to figure it out, k3s stores its kubernetes config in `/etc/rancher/k3s/k3s.yaml`, so the easiest is to: `export KUBECONFIG=/etc/rancher/k3s/k3s.yaml` and rerun the `operator-sdk olm install`
Take a look at those explicitly ignored errors - maybe some of them need attention and handling.
> Thx @JakubLedworowski one comment @Apokleos I reverted this one change, can we proceed to testing?
Closing as I am not able to finish work on this at the moment.