ContainerSolutions/externalsecret-operator

Include Helm chart setup again

Open

#96 opened on Oct 7, 2020

View on GitHubContributor guide
 (2 comments) (0 reactions) (2 assignees)Go (27 forks)auto 404
enhancementgood first issuehacktoberfesthelp wanted

Repository metrics

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

Description

Describe the solution you'd like

  • Helm chart setup added to the project.
  • CI testing the helm chart

What is the added value? Users can have more options to deploy the operator, being able to choose between plain yaml or helm.

Give us examples of the outcome

Maybe something similar with what we had before: https://github.com/ContainerSolutions/externalsecret-operator/tree/d2b6c9f9717f42b28b90be304252f674ec9e9079/deployments/helm

Or maybe using operator sdk to generate the helm chart already: https://sdk.operatorframework.io/docs/building-operators/helm/tutorial/

Contributor guide

Research direction
Review the previous Helm chart at the given link and adapt it to the current project. Also look into using the operator sdk to generate the Helm chart. Set up CI to test the chart.
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.
2
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
HelmKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65