Audit trail to manage configuration drift of Installerset managed resources

未关闭
#3,045 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
go, kubernetes

调研方向

首先跟踪 TektonConfig 和 TektonInstallerSet 如何生成和更新生成的 ConfigMap。定义审计记录必须保留哪些内容,包括之前的配置、操作者,以及是否发生了 TektonConfig 之外的更改。完成的标准应是形成一份达成共识且可实施的审计跟踪设计,并明确其对升级和手动更改的行为。

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

描述

kind/feature
Feature Request

Add support for retaining an audit record of changes made to resources managed by TektonInstallerSet.

Use Case

We frequently encounter situations where a user sets component configuration through the TektonConfig, but later manually updates the generated ConfigMap to a different value. Because this change is made directly to the resource not through TektonConfig, the TektonInstallerSet does not reconcile it (as there is no corresponding change in the TektonConfig).

During a subsequent upgrade, the installer set overwrites the manually modified values in the ConfigMap, restoring the defaults defined by the operator. Users then report issues because their custom configuration appears to have been “lost” after the upgrade.

This leads to significant troubleshooting overhead, as it is difficult to determine:

  • what the configuration previously was,
  • who changed it, and
  • whether it was modified manually outside of the operator workflow.

To address this, can we come up with solution that can retain or expose an audit trail of changes to resources managed by TektonInstallerSet, so that unexpected configuration overwrites can be diagnosed more easily.

cc: @aThorp96 @ab-ghosh

主要语言
Go
星标
606
派生
270
平均合并
1 天 7 小时
30 天内合并 PR
159

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tektoncd/operator 的其他 Issue

查看 tektoncd/operator 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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