kanisterio/kanister

Allow imagePullSecrets configurable on operator Deployment

Open

#2,999 opened on Jul 25, 2024

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Go (178 forks)auto 404
acceptedenhancementgood first issuehelp wanted

Repository metrics

Stars
 (883 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. Deployment for kanister-operator is quite limited in options, therefore it fails under many kube-score/kube-linter tests. Allowing more options to the deployment file would benefit from robustness perspective and best practices around helm chart creation. To list a few:

  • imagePullSecrets
  • containerSecurityContext
  • podSecurityContext
  • affinity
  • pdb (although not related to the deployment template file, related to the PDB object missing)
  • deployment strategy

Describe the solution you'd like Improve Deployment/Helm chart to make kanister-operator helm chart a more production ready option (currently won't work on Openshift for example)

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Environment Kubernetes Version/Provider: ... Storage Provider: ... Cluster Size (#nodes): ... Data Size: ...

Additional context Add any other context or screenshots about the feature request here.

Contributor guide

Research direction
Examine the existing Helm chart templates (especially deployment.yaml) and values.yaml in the repository. Identify where to add imagePullSecrets and other fields. Implement changes to allow configuration via Helm values, following the patterns of similar projects.
Tech stack
gokubernetes
Domain
infrastructuredevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesHelm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65