Add namespace level pruner config controller

[infernus01]

Changes

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

This enables namespaces to configure their own pruning policies. By creating a tekton-pruner-namespace-spec ConfigMap in a namespace, users can now set custom configurations(like TTL and history limits) that override global defaults.

[anithapriyanatarajan]

@infernus01 Thankyou for the PR. Please consider including a watcher in the namespace controller for namespace deletion. Whenever a namespace is deleted, update the configstore to remove the config values specific to the namespace.

[anithapriyanatarajan]

To make sure the role provides least required access please consider including the resourceName for get and watch atleast.

# List permission - required for informer setup (cannot use resourceNames)
- apiGroups:
    - ""
  resources:
    - configmaps
  verbs:
    - list

# Get/Watch permission - restricted to specific ConfigMap name
- apiGroups:
    - ""
  resources:
    - configmaps
  resourceNames:
    - tekton-pruner-namespace-spec
  verbs:
    - get
    - watch

[anithapriyanatarajan]

Please update the cluster role

[anithapriyanatarajan]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anithapriyanatarajan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [anithapriyanatarajan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[anithapriyanatarajan]

/lgtm