Add note about Bitnami allowInsecureImages flag for proxy registry#4091
Conversation
…ctors The SDK's built-in support bundle spec uses exec collectors to call internal API endpoints, but the pods/exec RBAC requirement was not documented. Without it, app-info.json and license.yaml are silently missing from bundles. This adds an RBAC requirements section to the customizing page and a troubleshooting entry to the generating page. sc-136407 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bitnami charts reject images from non-default registries with a misleading error. Document the workaround and clarify that the flag name does not indicate insecure connections. Closes #3989 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| 1. <RewriteHelmValues/> | ||
|
|
||
| :::note | ||
| Bitnami charts may display the error "Original containers have been substituted for unrecognized ones" when images are pulled from the Replicated proxy registry instead of the default Bitnami registry. To resolve this, set `global.security.allowInsecureImages=true` in your Helm values. Despite the name, this flag permits images from non-Bitnami registries. Your images are still pulled over HTTPS with authentication. |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'Bitnami'?
| 1. <RewriteHelmValues/> | ||
|
|
||
| :::note | ||
| Bitnami charts may display the error "Original containers have been substituted for unrecognized ones" when images are pulled from the Replicated proxy registry instead of the default Bitnami registry. To resolve this, set `global.security.allowInsecureImages=true` in your Helm values. Despite the name, this flag permits images from non-Bitnami registries. Your images are still pulled over HTTPS with authentication. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('been substituted').
| 1. <RewriteHelmValues/> | ||
|
|
||
| :::note | ||
| Bitnami charts may display the error "Original containers have been substituted for unrecognized ones" when images are pulled from the Replicated proxy registry instead of the default Bitnami registry. To resolve this, set `global.security.allowInsecureImages=true` in your Helm values. Despite the name, this flag permits images from non-Bitnami registries. Your images are still pulled over HTTPS with authentication. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('are pulled').
| 1. <RewriteHelmValues/> | ||
|
|
||
| :::note | ||
| Bitnami charts may display the error "Original containers have been substituted for unrecognized ones" when images are pulled from the Replicated proxy registry instead of the default Bitnami registry. To resolve this, set `global.security.allowInsecureImages=true` in your Helm values. Despite the name, this flag permits images from non-Bitnami registries. Your images are still pulled over HTTPS with authentication. |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'Bitnami'?
| verbs: ["create"] | ||
| ``` | ||
|
|
||
| Without this permission, the `exec` collectors fail silently. The support bundle is still generated and can be uploaded to the Vendor Portal, but `app-info.json` and `license.yaml` will be missing. The Vendor Portal displays warnings such as "No app-info file found" and "No license file found" when these files are absent. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('be uploaded').
|
|
||
| #### Cause | ||
|
|
||
| The Replicated SDK's built-in support bundle spec uses `exec` collectors to retrieve application and license information from the SDK pod. If the service account running the support bundle does not have `pods/exec` permissions with the `create` verb, these collectors fail silently and the data is not included in the bundle. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
Summary
allowInsecureImageserror and workaroundMultiple bootcamp participants hit this error when routing Bitnami subchart images through the Replicated proxy registry.
Closes #3989
Test plan
/vendor/helm-image-registry🤖 Generated with Claude Code