Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure Installer to set multiple pull secrets in image-builder-mk3 #10397

Closed
Tracked by #10298
mrsimonemms opened this issue Jun 1, 2022 · 4 comments
Closed
Tracked by #10298
Labels
meta: never-stale This issue can never become stale team: delivery Issue belongs to the self-hosted team

Comments

@mrsimonemms
Copy link
Contributor

mrsimonemms commented Jun 1, 2022

Amend the image-builder-mk3 configmap to reflect the new config for pullSecrets. This will require two values - the existing pull secret for the container registry and the imagePullSecret

@stale
Copy link

stale bot commented Sep 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 9, 2022
@mrsimonemms
Copy link
Contributor Author

Removing staleness

@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Sep 10, 2022
@kylos101 kylos101 added the meta: never-stale This issue can never become stale label Sep 10, 2022
@kylos101
Copy link
Contributor

👋 @mrsimonemms can you check the description? The # referenced (10397) indicates this depends on itself.

Also, do we have a workaround for this now in KOTS? I assume this is a workaround. In other words, do we have any users who cannot install Gitpod because of this issue, or are they okay because of the above PR?

I agree the product should be fixed long term so a workaround isn't needed. 👍

@mrsimonemms
Copy link
Contributor Author

@kylos101 good spot. I think that's an old comment, so I've removed it.

@mrsimonemms mrsimonemms closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2023
@github-project-automation github-project-automation bot moved this to Awaiting Deployment in 🌌 Workspace Team Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale team: delivery Issue belongs to the self-hosted team
Projects
No open projects
Status: Awaiting Deployment
Development

No branches or pull requests

2 participants