Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add helm chart to the release #829

Closed
eyusupov opened this issue Apr 29, 2019 · 30 comments
Closed

Add helm chart to the release #829

eyusupov opened this issue Apr 29, 2019 · 30 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@eyusupov
Copy link

eyusupov commented Apr 29, 2019 •
edited
Loading

OLM is already using helm to generate olm.yaml under the hood. It'd be nice to have the chart published as well, so that it could be installed like

helm install https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.9.0/olm.tar.gz
@ekarlso
Copy link

ekarlso commented Aug 14, 2019

Anyone from the devs care to weigh in on this?

@ecordell ecordell added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Dec 20, 2019
@ecordell
Copy link
Member

We don't intend to continue to use helm as our templating layer forever, so this has not been a high priority for us.

@stale
Copy link

stale bot commented Feb 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 26, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Feb 28, 2020
@RichiCoder1
Copy link

+1 for this, if only because it makes it super easy to use a tool like Flux to manage the OLM (which then manages everything else :D)

@benluddy benluddy mentioned this issue Mar 24, 2020
Merged
@kfox1111
Copy link

If folks step up to support this, would the project accept the pr's? It seems like a useful thing to support.

@stale
Copy link

stale bot commented Jun 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jun 28, 2020
@stale
Copy link

stale bot commented Aug 29, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 29, 2020
@RichiCoder1
Copy link

Bump

@stale stale bot removed the wontfix label Aug 29, 2020
@stale
Copy link

stale bot commented Oct 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 28, 2020
@stale
Copy link

stale bot commented Dec 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 28, 2020
@mkilchhofer
Copy link

Bump again. I am also interested in having a helm chart for managing OLM.

@timothymathison
Copy link

I'm also interested in this capability, so that we can manage the installation with the terraform helm provider.

@ikorzh
Copy link

ikorzh commented Feb 12, 2021 •
edited
Loading

This is a good idea.
I am also interested in having a helm chart for managing OLM

@sathieu sathieu mentioned this issue Jul 2, 2021
Closed
@yelhouti
Copy link

yelhouti commented Jul 3, 2021

interested in this two please

@yelhouti yelhouti mentioned this issue Jul 3, 2021
Open
@clayrisser
Copy link

Any update on this?

@sathieu
Copy link
Contributor

sathieu commented Aug 31, 2021 •
edited
Loading

I've published the chart here: https://gitlab.com/kubitus-project/external-helm-charts/operator-lifecycle-manager

It'll be updated automatically when new olm versions appears.

EDIT: updated URL

@chrisdewar
Copy link

Above gitlab.com link 404's for me... any update on this?

@sturman
Copy link

sturman commented Oct 9, 2021

@sathieu @chrisdewar Looks like the git repo has been moved to https://gitlab.com/kubitus-project/external-helm-charts/operator-lifecycle-manager. Helm repository address has not been changed and it still is https://gitlab.com/api/v4/projects/29255838/packages/helm/stable as mentioned in README. Also you can check available Helm repository packages in GitLab packages

@sathieu
Copy link
Contributor

sathieu commented Oct 9, 2021

@chrisdewar Sorry, I've just updated the URL above. As @sturman said, the repo has moved.

@sathieu
Copy link
Contributor

sathieu commented Oct 9, 2021

v0.19.1 was published 3 days ago, automatically, thanks to renovate.

@sturman
Copy link

sturman commented Oct 9, 2021

@sathieu the chart version 0.19.1 is not found in the repository. I can see version 0.19.0 only

user@think-t460p:~/projects$ helm search repo lifecycle
NAME                          	CHART VERSION	APP VERSION	DESCRIPTION                
operator-lifecycle-manager/olm	v0.19.0      	           	A Helm chart for Kubernetes
user@think-t460p:~/projects$

@sathieu
Copy link
Contributor

sathieu commented Oct 10, 2021

@sturman I don't have the same result:

$ helm repo add operator-lifecycle-manager https://gitlab.com/api/v4/projects/29255838/packages/helm/stable
"operator-lifecycle-manager" has been added to your repositories

$ helm search repo operator-lifecycle-manager
NAME                            CHART VERSION   APP VERSION     DESCRIPTION                
operator-lifecycle-manager/olm  v0.19.1                         A Helm chart for Kubernetes

$ helm search repo operator-lifecycle-manager -l
NAME                            CHART VERSION   APP VERSION     DESCRIPTION                
operator-lifecycle-manager/olm  v0.19.1                         A Helm chart for Kubernetes
operator-lifecycle-manager/olm  v0.19.0                         A Helm chart for Kubernetes

You are probably using the old repo:

$ helm repo add operator-lifecycle-manager-old https://gitlab.com/api/v4/projects/29255838/packages/helm/operator-lifecycle-manager
"operator-lifecycle-manager-old" has been added to your repositories

$ helm search repo operator-lifecycle-manager-old -lNAME                                    CHART VERSION   APP VERSION     DESCRIPTION                
operator-lifecycle-manager-old/olm      v0.19.0                         A Helm chart for Kubernetes
operator-lifecycle-manager-old/olm      v0.18.3                         A Helm chart for Kubernetes
operator-lifecycle-manager-old/olm      v0.18.1                         A Helm chart for Kubernetes

Some context: We needed this chart for Kubitus Installer, to install Keycloak Operator. Kubitus installer installs a full-featured Kubernetes cluster "batteries included" (see readme). It's still alpha, but beta is expected around December 2021.

@dinhxuanvu
Copy link
Member

We have no intention to release helm chart for OLM. It is not how OLM is being installed at the moment. We simply use helm for templating during release. We don't want to maintain a OLM helm chart either.

@nwmcsween
Copy link

nwmcsween commented Dec 13, 2021 •
edited
Loading

This can be done with argocd, specifiy the git repo and and targetRevision (release-xyz) add the helm deploy/chart as the helm dir.

@danielloader
Copy link

danielloader commented Jan 30, 2023 •
edited
Loading

For those using flux V2, this seems to work:

---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: GitRepository
metadata:
  name: olm
  namespace: flux-system
spec:
  interval: 1m0s
  ref:
    semver: ">= v0.23.1"
  url: https://github.com/operator-framework/operator-lifecycle-manager.git
  ignore: |
    # exclude all
    /*
    # include chart
    !/deploy/chart/
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: olm
  namespace: flux-system
spec:
  interval: 1m0s
  chart:
    spec:
      chart: ./deploy/chart/
      sourceRef:
        kind: GitRepository
        name: olm
        namespace: flux-system
      interval: 1m

Though I haven't worked out which is the least painful option:

  • Using Flux controllers as the source of truth to bootstrap the cluster and add OLM after via the above snippet, which adds all the operators to the cluster.
  • Using OLM CLI to bootstrap the cluster, adding fluxcd after via https://operatorhub.io/operator/flux and then run the flux CLI locally via bootstrap or install subcommands depending on if the upstream source cluster definition exists.

Will go play with either painful option.

@atropos112
Copy link

Thank you @sathieu for the chart and for maintaining it you are a ⭐ . As it stands the official install is a bash script. Maybe my understanding of what GitOps is is completely wrong but this looks like a red flag to me signaling that OLM is not GitOps friendly, a shame really given that the industry is heading towards GitOps & Operator direction and this is clearly a mess of an install to makes you choose one or the other...

@nick4fake
Copy link

@atropos112 running bash script for installation is opposite of declarative approach, so you are right. There should be defined with to use it with GitOps, especially counting the fact it's this project is base for operators doing exactly that :)

@acelinkio acelinkio mentioned this issue May 31, 2023
Open
@rowi1de
Copy link

rowi1de commented Oct 4, 2023 •
edited
Loading

@sturman I don't have the same result:

$ helm repo add operator-lifecycle-manager https://gitlab.com/api/v4/projects/29255838/packages/helm/stable
"operator-lifecycle-manager" has been added to your repositories

$ helm search repo operator-lifecycle-manager
NAME                            CHART VERSION   APP VERSION     DESCRIPTION                
operator-lifecycle-manager/olm  v0.19.1                         A Helm chart for Kubernetes

$ helm search repo operator-lifecycle-manager -l
NAME                            CHART VERSION   APP VERSION     DESCRIPTION                
operator-lifecycle-manager/olm  v0.19.1                         A Helm chart for Kubernetes
operator-lifecycle-manager/olm  v0.19.0                         A Helm chart for Kubernetes

thanks for that @sathieu 🙌🏻
did you consider adding your chart source here https://artifacthub.io/ ?

@sathieu
Copy link
Contributor

sathieu commented Oct 4, 2023

@rowi1de I'm currently moving away from OLM (which was only used to install keycloak-operator).

I've started a new Helm chart for Keycloak Operator Legacy (it's on artifacthub.io). I'm also working on Keycloak Operator (the new one, without KeycloakClient support) and I'll add it once it's ready.

@cornfeedhobo
Copy link

We don't intend to continue to use helm as our templating layer forever, so this has not been a high priority for us.

I don't know, 5+ years seems like long enough that it would have been nice to save everyone all this trouble 😞

@DreamingRaven DreamingRaven mentioned this issue Jun 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests