Links were never required by default unless you enabled the "require links for secrets" option. That option was dropped between 3.11 and 4.1 and is currently not supported.
On Thu, Sep 10, 2020 at 2:27 PM Just Marvin < marvin.the.cynical.ro...@gmail.com> wrote: > Clayton, > > Thanks for the response. "no longer required" as in this was a change > made recently? What version of OpenShift was this change made effective in? > > Thanks, > Marvin > > On Thu, Sep 10, 2020 at 10:02 AM Clayton Coleman <ccole...@redhat.com> > wrote: > >> Link is no longer required unless you want pods with that service account >> to use a pull secret automatically. Import isn't related to a service >> account, so it uses all pull secrets in the namespace. >> >> On Thu, Sep 10, 2020 at 9:25 AM Just Marvin < >> marvin.the.cynical.ro...@gmail.com> wrote: >> >>> Hi, >>> >>> I've observed that for an import-image to work, I don't need to link >>> my pull secret to a service account. I just need to create the secret. Yet, >>> there are other times when the link is absolutely required. (1) if the >>> import-image works without a link to a service account, it must be working >>> without using a service account. How does it know which secret to use for >>> pulling an image from an external registry? (2) If a secret "auto find" is >>> really possible, whats the point of this "link" step in circumstances where >>> it is needed today? >>> >>> Regards, >>> Marvin >>> _______________________________________________ >>> users mailing list >>> users@lists.openshift.redhat.com >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
