cloudnative-pg / cloudnative-pg/plugin-barman-cloud

Sidecar image with private registry & authentication in air-gapped environment

未关闭
#503 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
question
主要语言
Go
星标
192
派生
75
平均合并
1 天 16 小时
30 天内合并 PR
18

描述

Follow-up on https://github.com/cloudnative-pg/plugin-barman-cloud/issues/391

Hello,

I understand I can modify the location of the sidecar image with an env variable in the operator deployment and it works fine with our lab environment, where we use the harbor registry and no auth.
That said, we are required to use other registries from dev to prod environments and I don't understand how I can define imagePullSecrets for the sidecar container since it's not a regular PodSpec resource.

Any advice or suggestion ?

For the record, we transitioned all other images ( controllers + PG) to our internal registry with authentication, no issue.

Thanks

贡献指南

打开贡献指南

调研方向

首先跟进 issue #391,检查如何通过 operator deployment 配置 sidecar image。确定如何在 air-gapped 环境中为 sidecar 提供经过身份验证的 registry 凭据;当受支持的配置明确并且能在所描述的环境中运行时,即可完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
go, kubernetes
领域
devops, infrastructure
Issue 类型
功能
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。