Documentation: describe pull secret differences from OCP

[vrutkovs]

• "Fake" pull secret
• Optional pull secret in installer survey

[jxadro]

Hi, could you comment quicky what happens if we use the fake pull secret? Which are the limitations?

[vrutkovs]

• Telemetry and Insights operators would no longer send data to Red Hat servers
• Any content - like imagestreams and operators - from registry.redhat.io registry would be unavailable (registry.access.redhat.com would still be available though as it doesn't require a pull secret)

[kai-uwe-rommel]

In the OKD documentation, specifically in
https://docs.okd.io/latest/installing/installing_vsphere/installing-vsphere.html
it says:

"3. From the Pull Secret page on the Red Hat OpenShift Cluster Manager site, download your installation pull secret as a .txt file. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for OKD components."

Is it really OK to use a pull secret from the OpenShift Cluster Manager site for an OKD installation? What instead (in case that the OKD docs have not been updated correctly in this spot)?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[vrutkovs]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[bdlink]

Perhaps related to this, with 4.6 the samples operator does not fail, and does load samples, and templates, but get the alert

The samples operator cannot find credentials for 'registry.redhat.io'. Many of the sample ImageStreams will fail to import unless the 'samplesRegistry' in the operator configuration is changed.

Documentation does not indicate alternative registry to use when not using a RedHat pull secret. This information, along with a sample oc edit on how to configure would be useful.

[mburke5678]

@vrutkovs @jxadro Would adding a note like the following cover your concerns?

If you do not use the pull secret from the {cloud-redhat-com} site:

* Red Hat Operators are not available. 
* The Telemetry and Insights operators do not send data to Red Hat.
* Content from the [Red Hat Container Catalog](link:https://registry.redhat.io/) registry, such as image streams and Operators, are unavailable. 

openshift/openshift-docs#29061

[mburke5678]

/assign

[mburke5678]

/remove-lifecycle stale

[mburke5678]

/close

[openshift-ci-robot]

@mburke5678: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.