Skip to content

Add note about Bitnami allowInsecureImages flag for proxy registry#4091

Merged
AmberAlston merged 2 commits into
mainfrom
bitnami-allow-insecure-images-note
May 22, 2026
Merged

Add note about Bitnami allowInsecureImages flag for proxy registry#4091
AmberAlston merged 2 commits into
mainfrom
bitnami-allow-insecure-images-note

Conversation

@AmberAlston
Copy link
Copy Markdown
Member

Summary

  • Adds a note to the proxy registry Helm docs explaining the Bitnami allowInsecureImages error and workaround
  • Clarifies that the flag permits non-Bitnami registries, not insecure connections

Multiple bootcamp participants hit this error when routing Bitnami subchart images through the Replicated proxy registry.

Closes #3989

Test plan

  • Verify note renders correctly on the preview at /vendor/helm-image-registry
  • Confirm note placement makes sense after the registry rewrite step

🤖 Generated with Claude Code

AmberAlston and others added 2 commits May 22, 2026 10:27
…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>
@AmberAlston AmberAlston requested a review from a team as a code owner May 22, 2026 17:39
@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 3bc7ce0
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/6a1094b9b7cd7e0008733991
😎 Deploy Preview https://deploy-preview-4091--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 3bc7ce0
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/6a1094b9a5160f0008a0e6e7
😎 Deploy Preview https://deploy-preview-4091--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels May 22, 2026
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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.

@AmberAlston AmberAlston merged commit 96f38dd into main May 22, 2026
6 checks passed
@AmberAlston AmberAlston deleted the bitnami-allow-insecure-images-note branch May 22, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bitnami charts' "allowInsecureImages" flag name is misleading when using Replicated proxy

2 participants