You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since its inception, NetObserv has used OLM / OperatorHub as the only vector for shipping its releases. There are 2 channels for releases: the "community releases" on operatorhub.io, and the Red Hat branded ones for downstream OpenShift. Today, we are considering moving the community releases away from OLM/OperatorHub, to a more simple and direct Helm chart, which would simplify our community release process, allowing us to release more often.
This issue is labelled "Good first issue" : it doesn't require to have any knowledge on the NetObserv code base. I guess it only requires to have some knowledge about Helm and K8S. If you are interested to do that, just let us know by replying here. We can get in touch and will provide help. We're very open to have more community contributions, so this could be a starting point.
The text was updated successfully, but these errors were encountered:
Since its inception, NetObserv has used OLM / OperatorHub as the only vector for shipping its releases. There are 2 channels for releases: the "community releases" on operatorhub.io, and the Red Hat branded ones for downstream OpenShift. Today, we are considering moving the community releases away from OLM/OperatorHub, to a more simple and direct Helm chart, which would simplify our community release process, allowing us to release more often.
This issue is labelled "Good first issue" : it doesn't require to have any knowledge on the NetObserv code base. I guess it only requires to have some knowledge about Helm and K8S. If you are interested to do that, just let us know by replying here. We can get in touch and will provide help. We're very open to have more community contributions, so this could be a starting point.
The text was updated successfully, but these errors were encountered: